-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
root user has no permissions within container #884
Comments
See also docker-library/php#1192 |
Another workaround would be to add |
Upping the docker version fixed this for me
|
I got the same issue ( |
Fixes the docker build that was caused by docker-library/postgres#884. Using the alpine and version 13 image avoids the problem introduced with postgres 14 and debian bullseye.
My docker version is 20.10.20, but still has this issue. The magic comes out after upgrading the |
Fixes the docker build that was caused by docker-library/postgres#884. Using the alpine and version 13 image avoids the problem introduced with postgres 14 and debian bullseye.
Fixes the docker build that was caused by docker-library/postgres#884. Using the alpine and version 13 image avoids the problem introduced with postgres 14 and debian bullseye.
Issue seen in pg13
Specifically, when running a CI build in Travis (I think it happening within a Travis build is coincidental, but perhaps not). The postgres image is built using the
postgres
image with no tag specified. When the container is run, the following error occurs:The offending line of code is the following:
postgres/13/bullseye/docker-entrypoint.sh
Line 296 in c3bf1dd
After connecting to the running container (by setting the command to
sleep
), runningls -al
shows the following output:I don't understand why the root user has no permissions to anything in the filesystem.
The timing of this issue seems to correspond to the following commit, where the postgres change from
buster
tobullseye
was added to the official libraries in docker:docker-library/official-images@f21b412
I was able to get around the issue by specifying
image: postgres:buster
indocker-compose.yml
. The root cause is likely still unsolved in the wild.Here are the relevant sections of our
docker-compose.yml
:The text was updated successfully, but these errors were encountered: