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

Ubuntu 22.04 installs podman v3.4.4: Errors were encountered while processing golang-github-containers-image and golang-github-containers-common #1571

Closed
jefflill opened this issue May 25, 2022 · 7 comments
Assignees
Labels
bug Identifies a bug or other failure cluster-setup neonKUBE cluster setup debt Engineering debt neon-kube Related to our Kubernetes distribution

Comments

@jefflill
Copy link
Collaborator

Tracking: containers/podman#14367

Installing podman on Ubuntu 22.04 via apt-get fails with:

Errors were encountered while processing:
 /tmp/apt-dpkg-install-lvJTgR/01-golang-github-containers-image_5.16.0-3_all.deb
 /tmp/apt-dpkg-install-lvJTgR/02-golang-github-containers-common_0.44.4+ds1-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Important: Podman v3.4.4 is being installed here not the latest v4.1.0 build. Perhaps this is the underlying problem?

@jefflill jefflill added bug Identifies a bug or other failure neon-kube Related to our Kubernetes distribution cluster-setup neonKUBE cluster setup labels May 25, 2022
@jefflill jefflill self-assigned this May 25, 2022
@jefflill
Copy link
Collaborator Author

I've hacked NodePrepare.NodeInstallPodman() to ignore errors from the apt-get install podman command for now. Podman seems to be working OK even with these error messages.

We're going to leave this open to track what the Podman team does with this and hopefully I'll be able to revert this hack in the near future.

@jefflill
Copy link
Collaborator Author

jefflill commented May 25, 2022

The podman team closed this issue and referred me to the Debian package managers. I'm not quite sure how to submit an issue there and I need to move on, so I'm going to leave this be.

The problem seems to be that two google container related dependencies are trying to update the same file (AKA overlapping files). I'm going to try using the -o Dpkg::Options::="--force-overwrite" option as described here:

actions/runner-images#2703 (comment)

like:

sudo apt-get update -q
sudo apt-get install -yq podman -o Dpkg::Options::="--force-overwrite"

@jefflill
Copy link
Collaborator Author

We're seeing the same problem installing kubeadm

@jefflill
Copy link
Collaborator Author

jefflill commented May 25, 2022

The --force-overwrite hack seems to be working.

I'm going to leave this issue open though, so we can check whether this is still necessary in the future.

@jefflill jefflill added the debt Engineering debt label May 25, 2022
@vrothberg
Copy link

Ubuntu 22.04 ships Podman v3.4 (see https://packages.ubuntu.com/search?keywords=podman&searchon=names&suite=jammy&section=all).

@siretart may understand what's going on. Note that it's best to open issues or bugzillas against the specific Linux distribution as there is not much we can do upstream for dowstream packaging issues.

@siretart
Copy link

siretart commented May 27, 2022

The podman team closed this issue and referred me to the Debian package managers. I'm not quite sure how to submit an issue there and I need to move on, so I'm going to leave this be.

Please follow the instructions at https://www.debian.org/Bugs/Reporting for reporting bugs to debian. I highly recommend using the reportbug tool as instructed on that page.

As for the specific error, I'm unable to reproduce this issue with podman run -it --rm ubuntu:22.04 bash -c 'apt update && apt install -y podman' -- that command passes for me just fine.

The error output is probably missing the relevant part that would indicate why the package manager might be having difficulties.

The cases where --force-overwrite is helping indicates a bug in involved pacakges. Most of the time I help users with these symptoms it turns out they were using poorly maintained packages from non-official archives. I'd advise sticking with official packaging repositories -- they tend to undergo stricter QA checks and have higher quality.

@jefflill
Copy link
Collaborator Author

jefflill commented Jun 4, 2022

FIXED: We upgraded to Ubuntu 22.04 and where Podman is on the official mirrors now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies a bug or other failure cluster-setup neonKUBE cluster setup debt Engineering debt neon-kube Related to our Kubernetes distribution
Projects
None yet
Development

No branches or pull requests

3 participants