-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
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
Error exec /entrypoint.sh: no such file or directory when running Odoo 17 Docker image #507
Comments
From
From
Perhaps step four is doing something unexpected? |
Why not just start with the publicly available odoo:17 image? It is easy enough to extend that image with a Dockerfile like: FROM odoo:17
USER root
# customization
USER odoo |
I want to make my own image for odoo 17.2 |
Makes perfect sense, but IMHO, you shouldn't have to. See #385. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue: Error
exec /entrypoint.sh: no such file or directory
when running Odoo 17 Docker imageDescription:
When I build the Docker image for Odoo 17 using the following command:
docker build -t odoo17 .
And then run the container using:
I encounter the following error:
exec /entrypoint.sh: no such file or directory
Steps to Reproduce:
17.0
directory.docker build -t odoo17 .
docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:15
docker run -p 8069:8069 --name odoo --link db:db -t odoo17
Expected Behavior:
The Odoo container should start without errors, and the application should be accessible via
http://localhost:8069
.Actual Behavior:
The container fails to start, displaying the error message:
exec /entrypoint.sh: no such file or directory
.Additional Information:
entrypoint.sh
file exists in the17.0
directory and is referenced in the Dockerfile.I am unsure if my commands are incorrect or if there is an issue with the
entrypoint.sh
script. Any guidance or assistance would be greatly appreciated.Thank you!
The text was updated successfully, but these errors were encountered: