podman
No description set
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:kubic:libcontainers:unstable/podman && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_service | 0000000367 367 Bytes |
Comments 9
slitvak69 wrote
I am not sure why podman build failed for ubuntu 20.04. Golang is available according to my search Can you please rerun 4.2.1 package build on Ubuntu 20.04?
cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal
apt-cache search golang-1.16 golang-1.16 - Go programming language compiler - metapackage golang-1.16-doc - Go programming language - documentation golang-1.16-go - Go programming language compiler, linker, compiled stdlib golang-1.16-src - Go programming language - source files
Looked at recently pristine VM with 20.04 to avoid extra repos as well.
lsm5 wrote
go-1.16 is old already for buildah so I guess it's also going to cause trouble for podman. So, I'd rather not spend too much time on this until Ubuntu itself updates to a newer go
Curious.r wrote
Hello, I tried installing podman on raspberrypi OS (64bit) as follows:
But it won't work out:
lsm5 wrote
Thanks for letting me know. Btw, could you confirm if your raspberry pi repositories are configured to use either of debian sid/unstable or debian testing? If your repos are still pointed at debian stable, you will most likely run into installation issues as there are no repos here for debian stable.
I'll take a look at this and get back in a bit.
lsm5 wrote
Tried this on a fresh
debian:sid
container image. Worked just fine. Can you please try this on a fresh debian testing or unstable environment and let me know if you still face this issue?Also, if you continue to see this error, could you please try manually installing criu and see what it says? That'd give us some more info on the possible root cause.
Curious.r wrote
Thanks for your help. My repos do still point at debian stable, and I guess that's why something went wrong. The installation guide on the official website does not mention this. Thank you again for your patience.
lsm5 wrote
Ack! i'll update the installation docs to make it clearer. Thanks!
Jackenmen wrote
The
podman-docker
package tries to execute an executable at an incorrect path:Jackenmen wrote
Looks like it's fixed in the latest build, thank you!