Replies: 4 comments
-
probably it's due rootless (uids > 65536) as it's working in rootful mode, but the error message could be: Podman is using rootless mode, blablabla, needs to use rootful mode to circumvent the issue |
Beta Was this translation helpful? Give feedback.
-
I would not recommend root. As the error says you can add more uids to /etc/sub{u,g}id and run podman system migrate. To be honest since the machine is only used by one user I see no reason why we shouldn't just use a much bigger range when we init the machine. |
Beta Was this translation helpful? Give feedback.
-
looks like there is no
|
Beta Was this translation helpful? Give feedback.
-
@ibuziuk you will need to execute on the machine first. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Pulling an image reports the error:
Steps to reproduce the issue:
start a fresh podman machine (in my case it's a
4.3.0
podman on the remote machine and 4.3.1 on the client side)run the command:
podman pull quay.io/devfile/universal-developer-image:ubi8-latest
Describe the results you received:
Describe the results you expected:
image being pulled.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes/No
Additional environment details (AWS, VirtualBox, physical, etc.):
Beta Was this translation helpful? Give feedback.
All reactions