Replies: 7 comments 8 replies
-
This is not something that can be fixed upstream, also this is an older version of podman. Please try with the latest version. |
Beta Was this translation helpful? Give feedback.
-
@giuseppe PTAL |
Beta Was this translation helpful? Give feedback.
-
is podman already running inside a user namespace? What do you see with |
Beta Was this translation helpful? Give feedback.
-
user@user-Latitude-7410:~/imx-yocto-bsp/sources/meta-coretigo$ cat /proc/self/uid_map please notice: I am running with podman 3.4.2 I am attaching devshell for honister with my recipe + devshell for the kirksron with same recipe. hope this could help. |
Beta Was this translation helpful? Give feedback.
-
podman unshare cat /proc/self/uid_map |
Beta Was this translation helpful? Give feedback.
-
Name: cat user@user-Latitude-7410:~/imx-yocto-bsp/sources/meta-coretigo$ podman unshare podman pull postgres:14 |
Beta Was this translation helpful? Give feedback.
-
so it is already running in a user namespace where only one ID is mapped:
Podman won't work in such an environment. What you could try is to manually create yet another user namespace with |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
running on ubuntu 20.04 as build machine.
podman install on this machine is 3.4.2
when running from regular shell podman pull succesful
when running from honister version podman pull succesful
when running same recipe from kirkston version it fails.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Log data follows:
| DEBUG: Executing shell function do_pull_image
| cannot setresgid: Invalid argument
| panic: runtime error: invalid memory address or nil pointer dereference
| [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x5632d0bb17a0]
|
| goroutine 1 [running]:
| github.com/containers/podman/vendor/github.com/containers/common/libimage.(*Runtime).Pull(0x0, 0x5632d1b3d720, 0xc0007b56e0, 0xc0001f9c90, 0xb, 0x0, 0xc000159a40, 0x0, 0x0, 0x0, ...)
| /usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/containers/common/libimage/pull.go:117 +0x500
| github.com/containers/podman/pkg/domain/infra/abi.(*ImageEngine).Pull(0xc00012c3d0, 0x5632d1b3d720, 0xc0007b56e0, 0x7ffde5cbbe0c, 0xb, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
| /usr/src/packages/BUILD/src/github.com/containers/podman/pkg/domain/infra/abi/images.go:231 +0x1e5
| github.com/containers/podman/cmd/podman/images.imagePull(0x5632d26d5e20, 0xc0000894f0, 0x1, 0x1, 0x0, 0x0)
| /usr/src/packages/BUILD/src/github.com/containers/podman/cmd/podman/images/pull.go:160 +0x2d5
| github.com/containers/podman/vendor/github.com/spf13/cobra.(*Command).execute(0x5632d26d5e20, 0xc00003c1a0, 0x1, 0x1, 0x5632d26d5e20, 0xc00003c1a0)
| /usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/spf13/cobra/command.go:856 +0x47c
| github.com/containers/podman/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x5632d26e7120, 0xc00004a188, 0x5632d1886480, 0x5632d27a98f0)
| /usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/spf13/cobra/command.go:974 +0x375
| github.com/containers/podman/vendor/github.com/spf13/cobra.(*Command).Execute(...)
| /usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/spf13/cobra/command.go:902
| github.com/containers/podman/vendor/github.com/spf13/cobra.(*Command).ExecuteContext(...)
| /usr/src/packages/BUILD/src/github.com/containers/podman/vendor/github.com/spf13/cobra/command.go:895
| main.Execute()
| /usr/src/packages/BUILD/src/github.com/containers/podman/cmd/podman/root.go:91 +0xee
| main.main()
| /usr/src/packages/BUILD/src/github.com/containers/podman/cmd/podman/main.go:39 +0x94
| WARNING: exit code 2 from a shell command.
Describe the results you expected
image should be download to local disk.
possible to list it using podman images in any shell.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
running on yocto kirkstone.
same recipe was working fine on same buid machine and same podman but on yocto honister version.
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
Beta Was this translation helpful? Give feedback.
All reactions