-
Notifications
You must be signed in to change notification settings - Fork 426
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Cannot run rabbitmq:3.8.16 image due to permissions errors #488
Comments
I am unable to reproduce with the plain |
I also face the same issue. I followed [guide](docker run -it --rm --name rabbitmq -p 5672:5672 -p 15672:15672 rabbitmq:3-management) but results to For 3.8.15 it works perfectly |
No flags, the command I posted is literally the one used to run the image, and the total command output is included. I'll see if I can modify the entrypoint script to get it to tell me what's going on once it hits the file(s) it thinks it doesn't have permissions on. |
If it helps, we don't seem to have the issue with the Alpine version of the image, so might switch to running that instead. |
I have the same issue, maybe related to docker version. On docker version 18.06.3-ce fail, version 18.09.0 pass. |
i have the same issue on my raspberrypi 4 it is returning the error: it works while using the following image: edit |
@NL-TCH what you're missing is opencontainers/runc#2750 -- you need a newer |
... which actually might be at least related to the underlying issue for the OP here? Can anyone reproduce with up-to-date Docker + runc? |
on the raspberry pi i already had docker version 20.10.7 (build f0df350) |
@NL-TCH I had the same issue, fixed it by updating libseccomp2 on my pi 4 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Since the rabbitmq:latest and rabbitmq:management images were pushed as a result of the 3.8.16 update, we're seeing permissions errors when trying to run those images in our CI environment:
Running the previous image is successful:
We don't do anything special with these images other than run them, but noticed the base image for rabbitmq has been bumped to ubuntu:20.04 in this update, not sure if that's causing the issue somehow? (We can run the image ubuntu:20.04 perfectly OK for what it's worth).
The text was updated successfully, but these errors were encountered: