Cannot pull docker image jgraph/export-server with podman

[keestux]

Hi,

Pulling the image jgraph/export-server (with podman) fails with this error:

Trying to pull docker.io/jgraph/export-server:latest...
Getting image source signatures
Copying blob ed6780dca0fb done  
Copying blob 0e6bcdd91e07 skipped: already exists  
Copying blob 61769084203c skipped: already exists  
Copying blob bb263680fed1 skipped: already exists  
Copying blob b72d40ede1f7 skipped: already exists  
Copying blob 3657d8059242 done  
Copying blob 90145816ab6f skipped: already exists  
Error: writing blob: adding layer with blob "sha256:ed6780dca0fb02e330b694fb41f1a7395d3b19b6773a21f32d67e5a0bcaf830e": processing tar file(potentially insufficient UIDs or GIDs available in user namespace (requested 110779:100 for /usr/local/drawio/draw-image-export2/node_modules/optionator/CHANGELOG.md): Check /etc/subuid and /etc/subgid if configured locally and run podman-system-migrate: lchown /usr/local/drawio/draw-image-export2/node_modules/optionator/CHANGELOG.md: invalid argument): exit status 1

Possibly there is a file with uid:gid that does not fit in my subuid range.

Where can I find the Dockerfile that was used to build this image?

[keestux]

This image is probably created on a system with large uid values. Or the subuid is set too broadly.

I believe it serves no purpose to allow such high uid values. At the same time it hinders podman environments with a default installation (subuid range 65536).

[m-mohamedin]

Hi,

I'm not an expert with podman, can you please explain the problem with setting UIDs range high?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. See the FAQ for more information.