Replies: 3 comments 2 replies
-
Interesting problem. I first tried to write a Containerfile to reproduce the error message that you see:
I'm assuming you are running rootless Podman.
Experiment 1: failure
Experiment 2: failure (image commit fails)
Experiment 3: success (configuring
|
Beta Was this translation helpful? Give feedback.
-
Thanks a lot for your experiment and comments. Here is my case details: I have a user s-dmadminua in container: Run the container: Got the error: How to identify which uid is conflict? |
Beta Was this translation helpful? Give feedback.
-
Here is the new podman run commands and error messages: podman run -it --rm --name dctmsvr --hostname dctmsvr --memory 16g --log-level debug DEBU[0002] Failed to create container dctmsvr(8ae904f9002d2307e821ec86a37cfe33b0fafc1df597ebc9c66daf6695a4ef11): the specified UID and/or GID mapping 1293208:50000:1 conflicts with other mappings: invalid mappings specified |
Beta Was this translation helpful? Give feedback.
-
I am doing an application containerization from RHEL 8.9 to OpenShift. My DEV environment is podman 4.61 on RHEL 8.9. Since the application and its huge data are owned by a user with uid=1293208 gid=1293060 on RHEL, I created the same UID and GID in the dockerfile. When creating a directory /opt/dmap and RUN chown -R uid:gid /opt/dmap, the chown failed with error: chown: changing ownership of '/opt/dmap': Invalid argument. But if using uid=10001, gid=1002, the chown works. Is there anyway to make the chown working for larg uid and gid?
Beta Was this translation helpful? Give feedback.
All reactions