We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have the folowwing error when i start my container : /docker-entrypoint.sh: ignoring /docker-entrypoint-initnuxeo.d/nuxeo.conf
/docker-entrypoint.sh: ignoring /docker-entrypoint-initnuxeo.d/nuxeo.conf
I verified if the file was there and it is.
I'm running the Folowing dockerFile from the docs
FROM nuxeo:10.10 COPY ./nuxeo.conf /docker-entrypoint-initnuxeo.d/nuxeo.conf
What i'm i supposed to do to make docker-entrypoint.sh running ?
The text was updated successfully, but these errors were encountered:
Hi,
The message you're getting is not an error, it's simply a log to inform that /docker-entrypoint-initnuxeo.d/nuxeo.conf isn't handled as the other files that could be existing in /docker-entrypoint-initnuxeo.d/ (.zip, .sh or .clid), see https://github.com/nuxeo/docker-nuxeo/blob/master/10.10/docker-entrypoint.sh#L52. It's as a special case since nuxeo.conf is already handled above, see https://github.com/nuxeo/docker-nuxeo/blob/master/10.10/docker-entrypoint.sh#L39.
/docker-entrypoint-initnuxeo.d/nuxeo.conf
/docker-entrypoint-initnuxeo.d/
nuxeo.conf
This shouldn't prevent the container from starting. If that's the case then there's another issue.
Closing the PR, feel free to open a new one if you're facing issues starting the Docker image.
Sorry, something went wrong.
No branches or pull requests
I have the folowwing error when i start my container :
/docker-entrypoint.sh: ignoring /docker-entrypoint-initnuxeo.d/nuxeo.conf
I verified if the file was there and it is.
I'm running the Folowing dockerFile from the docs
What i'm i supposed to do to make docker-entrypoint.sh running ?
The text was updated successfully, but these errors were encountered: