Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman build fails in kicbase image #8063

Closed
afbjorklund opened this issue May 10, 2020 · 13 comments · Fixed by #8774
Closed

podman build fails in kicbase image #8063

afbjorklund opened this issue May 10, 2020 · 13 comments · Fixed by #8774
Assignees
Labels
co/docker-driver Issues related to kubernetes in container co/podman-driver podman driver issues co/runtime/crio CRIO related issues kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented May 10, 2020

The latest/greatest podman for ubuntu, as used in the kicbase, hangs forever when trying to build:

 podman-remote version
Client:
Version:            1.9.1
RemoteAPI Version:  1
Go Version:         go1.13.8
Git Commit:         37a3aa6c83603ec774939a8d07c950dd3b26110a
Built:              Sun May 10 19:03:51 2020
OS/Arch:            linux/amd64

Server:
Version:            1.9.1
RemoteAPI Version:  1
Go Version:         go1.12.10
OS/Arch:            linux/amd64
  podman-remote build .
^C

Downgrading to the stable 1.8.2 version as used in the image, makes the build pass correctly again...

 podman-remote version
Client:
Version:            1.9.1
RemoteAPI Version:  1
Go Version:         go1.13.8
Git Commit:         37a3aa6c83603ec774939a8d07c950dd3b26110a
Built:              Sun May 10 19:03:51 2020
OS/Arch:            linux/amd64

Server:
Version:            1.8.2
RemoteAPI Version:  1
Go Version:         go1.13.8
Git Commit:         028e3317eb1494b9b2acba4a0a295df80fae66cc
Built:              Sun May 10 19:58:45 2020
OS/Arch:            linux/amd64
 podman-remote build .
STEP 1: FROM busybox
STEP 2: RUN true
--> Using cache 98bc298a4242e40d67a4f37d2a2d37f2cf7ab3b71e1499a67a278bd131e20398
98bc298a4242e40d67a4f37d2a2d37f2cf7ab3b71e1499a67a278bd131e20398

The kicbase has the prevision version 1.9.0, but unfortunately upgrading to 1.9.1 didn't work:

The following packages will be upgraded:
  podman
1 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
Need to get 21.0 MB of archives.

Get:1 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_19.10 podman 1.9.1~1 [21.0 MB]

Setting up podman (1.9.1~1) ...

And the stable versions like 1.6.5 or 1.8.2, are not available for "xUbuntu_19.10" (only RHEL)

@afbjorklund afbjorklund added kind/bug Categorizes issue or PR as related to a bug. co/runtime/crio CRIO related issues co/docker-driver Issues related to kubernetes in container co/podman-driver podman driver issues labels May 10, 2020
@afbjorklund
Copy link
Collaborator Author

The workaround is to building using ssh (with sudo podman build), as described in the manual.

This is only a problem when using podman/crio, since building with docker/containerd works OK.

It also has an upgrade pending, though. (due to the deb versions unfortunately being pinned down)

Unpacking docker.io (19.03.6-0ubuntu1~19.10.1) over (19.03.2-0ubuntu1) ...

@medyagh medyagh added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 11, 2020
@medyagh medyagh added this to the v1.11.0 milestone May 11, 2020
@afbjorklund
Copy link
Collaborator Author

Most likely need to build a custom .deb for 1.8.2, since the old packages are deleted.

NOTICE: 'podman' packaging is maintained in the 'Git' version control system at:
https://gitlab.com/lsm5/podman.git
Please use:
git clone https://gitlab.com/lsm5/podman.git
to retrieve the latest (possibly unreleased) updates to the package.

Also containers/podman#3924

@afbjorklund
Copy link
Collaborator Author

Same situation with Ubuntu 20.04 and Podman 1.9.2, so needs a special package.

podman/now 1.9.2~3 amd64 [installed,local]

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented May 24, 2020

I was able to build my own deb package for ubuntu focal, which fixes the problem.

podman/now 1.8.2~2 amd64 [installed,upgradable to: 1.9.2~3]

Only need some suitable place to host the package, so that it can be downloaded:

19M	podman_1.8.2~2_amd64.deb

All the old deb packages had been deleted, and the package failed to build from source:

See containers/podman#6240 (comment)

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman?rev=137

You need an opensuse account, to log in.

podman_1.8.2~2.dsc
podman_1.8.2~2.tar.gz

But when those are fixed, it builds easily:

sudo pbuilder create --basetgz /var/cache/pbuilder/focal.tgz --distribution focal
sudo pbuilder build --basetgz /var/cache/pbuilder/focal.tgz --distribution focal podman_1.8.2~2.dsc

See https://wiki.ubuntu.com/PbuilderHowto

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented May 24, 2020

https://dl.bintray.com/afbjorklund/podman/pool/main/p/podman/:podman_1.8.2~2_amd64.deb

Using the command line, add the following to your /etc/apt/sources.list system config file:
echo "deb https://dl.bintray.com/afbjorklund/podman {distribution} {components}" | sudo tee -a /etc/apt/sources.list

@afbjorklund
Copy link
Collaborator Author

Fix added to the ubuntu 20.04 version: PR #8251, as c6f5ba7

Requires a signed deb repository, for apt to properly accept it.

@afbjorklund afbjorklund modified the milestones: v.1.12.0, v1.11.0 May28 May 24, 2020
@afbjorklund
Copy link
Collaborator Author

Will try to get this included in 1.11 (with ubuntu 20.04 upgrade)

If that new image doesn't make it, they both go in 1.12 instead

@afbjorklund afbjorklund linked a pull request May 24, 2020 that will close this issue
@afbjorklund
Copy link
Collaborator Author

Works OK, with the new kicbase.

 podman-remote version
Client:
Version:            1.9.2
RemoteAPI Version:  1
Go Version:         go1.10.1
OS/Arch:            linux/amd64

Server:
Version:            1.8.2
RemoteAPI Version:  1
Go Version:         go1.13.8
OS/Arch:            linux/amd64
 podman-remote build .
STEP 1: FROM busybox
Getting image source signatures
Copying blob sha256:d9cbbca60e5f0fc028b13c01e70e96cc2eefe7858ccc5a33c9a8faa8b03286aa
Copying config sha256:78096d0a54788961ca68393e5f8038704b97d8af374249dc5c8faec1b8045e42
Writing manifest to image destination
Storing signatures
STEP 2: RUN true
STEP 3: COMMIT
--> 2207249a123
2207249a1231ffed51a6be64b21533113f9cc704f3401c1f3dcec5da918c3901

@medyagh medyagh modified the milestones: v1.11.0 May28, v.1.12.0 May 26, 2020
@afbjorklund
Copy link
Collaborator Author

Same situation with Ubuntu 20.04 and Podman 1.9.2, so needs a special package.

Podman 1.9.3 is now available, which fixes this issue.

podman/unknown,now 1.9.3~1 amd64 [installed]

(and that also means that podman 1.9.2 is unavailable)

@afbjorklund
Copy link
Collaborator Author

It doesn't work out-of-the-box with the docker driver, but most people use podman with cri-o.

error running container: error configuring network list if0 for [/bin/sh -c true]: failed to set bridge addr: could not add IP address to "cni0": permission denied

This is due to a different bug, just something for the testers...

See #7380

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Jul 1, 2020

Sadly now we might need to downgrade from 2.0.1 to 1.9.3

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman?rev=285

Will rebuild the package, and I suppose same for cri-o 1.18.2

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable:cri-o:1.18/cri-o?rev=6

@afbjorklund
Copy link
Collaborator Author

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Jul 19, 2020

Need to build a version for eoan as well, since it is currently broken and since the repo only has podman v2 now.

Setting up podman-plugins (0.0.0~1) ...
Setting up podman (2.0.2~2) ...

The old image (v0.0.10) still has podman 1.9.0, which needs to be changed to either 1.8.2 or 1.9.3 for build to work:

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman?rev=137 (podman_1.8.2~2.dsc)

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman?rev=285 (podman_1.9.3~1.dsc)

We used 1.8.2 for 1.11 and 1.9.3 for 1.12

 git diff -G PODMAN_VERSION v1.11.0 v1.12.0 deploy/iso/minikube-iso/package/podman/
diff --git a/deploy/iso/minikube-iso/package/podman/podman.mk b/deploy/iso/minikube-iso/package/podman/podman.mk
index ccc3af60b..57c2976e2 100644
--- a/deploy/iso/minikube-iso/package/podman/podman.mk
+++ b/deploy/iso/minikube-iso/package/podman/podman.mk
@@ -1,5 +1,5 @@
-PODMAN_VERSION = v1.8.2
-PODMAN_COMMIT = 028e3317eb1494b9b2acba4a0a295df80fae66cc
+PODMAN_VERSION = v1.9.3
+PODMAN_COMMIT = 5d44534fff6877b1cb15b760242279ae6293154c
 PODMAN_SITE = https://github.com/containers/libpod/archive
 PODMAN_SOURCE = $(PODMAN_VERSION).tar.gz
 PODMAN_LICENSE = Apache-2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/docker-driver Issues related to kubernetes in container co/podman-driver podman driver issues co/runtime/crio CRIO related issues kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
3 participants