podman: apt-get reports wrong file size for podman_3.4.2-1_amd64.deb in provo-mirror.opensuse.org

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

I’m unable to install Podman from Kubic repo on Ubuntu 20.04 LTS. I’ve tried on multiple Ubuntu machines many times today, but I get the same error each time.

Steps to reproduce the issue:

  1. Run installation commands from Podman docs
echo "deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/ /" | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list
curl -L "https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/Release.key" | sudo apt-key add -
sudo apt-get update
sudo apt-get -y upgrade
sudo apt-get -y install podman

Describe the results you received: Podman installation fails with error:

Err:1 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  podman 100:3.4.2-1
  File has unexpected size (17679080 != 17706544). Mirror sync in progress? [IP: 91.193.113.70 443]
  Hashes of expected file:
   - SHA256:4eb9b58413f602cf18ec21a742acd99ae10e71df467e7b9a63c3b1f7e8229f16
   - SHA1:cf1fefe5c85321fe9b562339a79494c9eda9dd60 [weak]
   - MD5Sum:58fa232055dff2700aa55e13c7932536 [weak]
   - Filesize:17706544 [weak]
E: Failed to fetch https://provo-mirror.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/amd64/podman_3.4.2-1_amd64.deb  File has unexpected size (17679080 != 17706544). Mirror sync in progress? [IP: 91.193.113.70 443]
   Hashes of expected file:
    - SHA256:4eb9b58413f602cf18ec21a742acd99ae10e71df467e7b9a63c3b1f7e8229f16
    - SHA1:cf1fefe5c85321fe9b562339a79494c9eda9dd60 [weak]
    - MD5Sum:58fa232055dff2700aa55e13c7932536 [weak]
    - Filesize:17706544 [weak]

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally): I’ve tried on multiple Ubuntu machines many times today, but I get the same error each time. I have found a similar issue with Opensuse hosted repo recently, but none regarding podman: https://github.com/cri-o/cri-o/issues/5802

Output of podman version: N/A - podman cannot be installed

Package info (e.g. output of rpm -q podman or apt list podman):

user@user-dev:~$ apt list podman
Listing... Done
podman/unknown 100:3.4.2-1 amd64
podman/unknown 100:3.4.2-1 arm64
podman/unknown 100:3.4.2-1 armhf
podman/unknown 100:3.4.2-1 s390x

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

No - Cannot install podman

Additional environment details (AWS, VirtualBox, physical, etc.):

Device environment:

Ubuntu 20.04.4 LTS (GNU/Linux 5.13.0-40-generic x86_64)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 7
  • Comments: 48 (20 by maintainers)

Most upvoted comments

3.4.2-5 has just been built and should now be available. Please give it a try. Thanks.

@lsm5, Looks like the mirror is out of sync again. Ubuntu1804:

    azure-arm:   File has unexpected size (18660200 != 18684404). Mirror sync in progress? [IP: 91.193.113.70 443]
    azure-arm:   Hashes of expected file:
    azure-arm:    - SHA256:260ac686758f6ed9160b99642ce278d7b175e3f354b31c7b3076653449e53ca4
    azure-arm:    - SHA1:a46da407925b088b8e2f3ec02a83817ce9003cf0 [weak]
    azure-arm:    - MD5Sum:1e98238abb397cbd3b006906ddd9a433 [weak]
    azure-arm:    - Filesize:18684404 [weak]
    azure-arm: Get:19 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04  skopeo 100:1.5.0-3 [6319 kB]
    azure-arm: Get:20 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04  slirp4netns 100:1.1.8-4 [691 kB]
    azure-arm: Get:21 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04  containernetworking-plugins 100:1.1.1~1 [7006 kB]
    azure-arm: Fetched 26.5 MB in 10s (2605 kB/s)
==> azure-arm: E: Failed to fetch https://provo-mirror.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04/amd64/podman_3.4.2-4_amd64.deb  File has unexpected size (18660200 != 18684404). Mirror sync in progress? [IP: 91.193.113.70 443]
==> azure-arm:    Hashes of expected file:
==> azure-arm:     - SHA256:260ac686758f6ed9160b99642ce278d7b175e3f354b31c7b3076653449e53ca4
==> azure-arm:     - SHA1:a46da407925b088b8e2f3ec02a83817ce9003cf0 [weak]
==> azure-arm:     - MD5Sum:1e98238abb397cbd3b006906ddd9a433 [weak]
==> azure-arm:     - Filesize:18684404 [weak]
==> azure-arm: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? 

Ubuntu2004:

    azure-arm: Err:22 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  podman 100:3.4.2-4
    azure-arm:   File has unexpected size (18676884 != 18659032). Mirror sync in progress? [IP: 91.193.113.70 443]
    azure-arm:   Hashes of expected file:
    azure-arm:    - SHA256:ef68bbab3752d524ec6be1b94f47a645dfc985b1ac497fc8ef7768278f560048
    azure-arm:    - SHA1:abe4b75985be6e70a1768032df4fcfc27f0f0d30 [weak]
    azure-arm:    - MD5Sum:aa95d7eb1bc9ca28edd3ef9b3a37805c [weak]
    azure-arm:    - Filesize:18659032 [weak]
    azure-arm: Get:23 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  skopeo 100:1.5.0-3 [6325 kB]
    azure-arm: Get:24 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  slirp4netns 100:1.1.8-4 [708 kB]
    azure-arm: Get:25 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  containernetworking-plugins 100:1.1.1~1 [7009 kB]
    azure-arm: Fetched 27.1 MB in 9s (2910 kB/s)
==> azure-arm: E: Failed to fetch https://provo-mirror.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/amd64/podman_3.4.2-4_amd64.deb  File has unexpected size (18676884 != 18659032). Mirror sync in progress? [IP: 91.193.113.70 443]
==> azure-arm:    Hashes of expected file:
==> azure-arm:     - SHA256:ef68bbab3752d524ec6be1b94f47a645dfc985b1ac497fc8ef7768278f560048
==> azure-arm:     - SHA1:abe4b75985be6e70a1768032df4fcfc27f0f0d30 [weak]
==> azure-arm:     - MD5Sum:aa95d7eb1bc9ca28edd3ef9b3a37805c [weak]
==> azure-arm:     - Filesize:18659032 [weak]
==> azure-arm: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

@rachnajain-ibm Try to install podman with --install-recommends option. Something like this

sudo apt-get -qq install --yes --install-recommends podman

I have reverted my decision mentioned in https://github.com/containers/podman/issues/14278#issuecomment-1131743956 given all the community demand.

podman, buildah and skopeo are back on the kubic repo and should be available for installation soon. Beware that podman is still only v3.4.2 and comes with all the issues associated with it. Please do consider using alternatives mentioned in earlier comments.

@al-cheb hi, so the new repo at https://build.opensuse.org/project/show/devel:kubic:libcontainers:unstable does seem to have packages built successfully and if everything goes well, it would be nice to use it (or a branch of it) in github actions and wherever else people need to use container tools on ubuntu 20.04, 18.04 and also debian 11. But we would really need some prior testing done. So, could you let me know if github actions has a workflow to determine if this repo is ready for deployment?

I’m fixing the hash mismatch issue now.

Long term I think it’s best I just get https://build.opensuse.org/project/show/devel:kubic:libcontainers:unstable in good enough shape that ubuntu users can just use that one. That should make everyone happy including myself.

@lospringliu yes, but hope that works for you though. The latest version of fuse-overlayfs needed fuse3 and restoring the archive was gonna be a lot more painful than I imagined. And I also had to build for newer ubuntu, so that’s why.

Ah, good catch, thanks 😦 Does anyone know what the rationale is? Unless Canonical are going upgrade podman in SRUs (seems unlikely given it seems to be in ‘universe’), this is going to make it a lot harder to track the latest release 😦

@srd424 the debian way of packaging was proving to be just too painful to maintain and automate. My wip repo in the last comment generates deb packages using fedora’s packaging sources which should be a lot easier to maintain and update (I hope). The initial plan was to only use it for ubuntu testing in upstream CI but if anyone in the community is willing to try things out then I figured why not.