Cannot run rabbitmq:3.8.16 image due to permissions errors #518
Replies: 10 comments
-
I am unable to reproduce with the plain |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue, maybe related to docker version. On docker version 18.06.3-ce fail, version 18.09.0 pass. |
Beta Was this translation helpful? Give feedback.
-
i have the same issue on my raspberrypi 4 it is returning the error: it works while using the following image: edit |
Beta Was this translation helpful? Give feedback.
-
@NL-TCH what you're missing is opencontainers/runc#2750 -- you need a newer |
Beta Was this translation helpful? Give feedback.
-
... which actually might be at least related to the underlying issue for the OP here? Can anyone reproduce with up-to-date Docker + runc? |
Beta Was this translation helpful? Give feedback.
-
on the raspberry pi i already had docker version 20.10.7 (build f0df350) |
Beta Was this translation helpful? Give feedback.
-
@NL-TCH I had the same issue, fixed it by updating libseccomp2 on my pi 4 |
Beta Was this translation helpful? Give feedback.
-
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).
Beta Was this translation helpful? Give feedback.
All reactions