Skip to content

podman pull quay.io/devfile/universal-developer-image:ubi8-latest failing #873

@themr0c

Description

@themr0c

/kind bug
/area developer-images

What versions of software are you using?

Operating System: Fedora 36

Go Pkg Version: --

podman version 4.1.0

Bug Summary

Describe the bug:

I can't pull the universal-developer image on a rootless podman environment, on Fedora 36 with a BTRFS filesystem.

To Reproduce:

  1. Verify podman subuid and subgid are configured:
$ cat /etc/subuid
ffloreth:200000:65536
$ cat /etc/subgid
ffloreth:200000:65536
  1. Pull the image:
$ podman pull quay.io/devfile/universal-developer-image:ubi8-latest
... 
Error: writing blob: adding layer with blob "sha256:68d68a40ee2a686776d48c8d10749be3478a20322a98ee53038fa4733b27bd11": Error processing tar file(exit status 1): potentially insufficient UIDs or GIDs available in user namespace (requested 0:1000640000 for /usr/local/bin/tkn): Check /etc/subuid and /etc/subgid if configured locally and run podman-system-migrate: lchown /usr/local/bin/tkn: invalid argument
  1. Reproduce same behavior on a container based on ubi:
$ podman pull quay.io/mloriedo/che-docs:2370

Expected behavior

  • Podman pulls the image without error.

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.

$ podman pull quay.io/devfile/universal-developer-image
... 
Error: writing blob: adding layer with blob "sha256:68d68a40ee2a686776d48c8d10749be3478a20322a98ee53038fa4733b27bd11": Error processing tar file(exit status 1): potentially insufficient UIDs or GIDs available in user namespace (requested 0:1000640000 for /usr/local/bin/tkn): Check /etc/subuid and /etc/subgid if configured locally and run podman-system-migrate: lchown /usr/local/bin/tkn: invalid argument

Additional context

Any workaround?

Suggestion on how to fix the bug

Metadata

Metadata

Assignees

Labels

developer-imagesIssues belonging to the developer-images repokind/bugSomething isn't workinglifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.lifecycle/staleStale items. These items have not been updated for 90 days.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions