-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
apt-get reports wrong file size for podman_3.4.2-1_amd64.deb in provo-mirror.opensuse.org #14278
Comments
I can verify this one too, I'm having exactly the same issue with same hashes and file sizes. Cannot proceed with the installation due to security risks. |
We have the same issue [Azure location: Central Us and West US2 ]- https://github.visualstudio.com/virtual-environments/_build/results?buildId=125926&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=5431112d-2b61-5a5f-7042-ef698f761043
|
@lsm5, Could you please take a look? |
I'm having the same issue: |
If anyone wants the beginnings of an insecure bodgy script to manually download the debs, try:
|
FWIW, the 22.04 repository seems to be broken too, some packages missing? |
"NOTE: Kubic packages have been discontinued for Ubuntu 22.04 LTS. Current users of the Kubic repos for Ubuntu are highly recommended to uninstall the packages from the Kubic repos before upgrading to Ubuntu 22.04 LTS." You should be able to just install from the Ubuntu repos if I'm reading the installation instructions correctly. |
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 :( |
Thanks @dokuhebi. @srd424 the 22.04 Kubic repository enablement was a mistake. That project is shared with the cri-o maintainers and they enabled 22.04 which ended up with podman getting enabled as well. For 22.04, you're way better off using ubuntu's own repos. The hash mismatch looks like a stale / out-of-sync mirror to me. Perhaps best to download the debs like @srd424 mentioned or try a different mirror https://mirrors.opensuse.org/list/bs.html I realize the presence of the podman package on that Kubic repo is causing more problems than solving. So, come Monday, I'll delete the package from there. Please download the debs from there before then. There are also a few other options:
Proceed with caution: |
@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. |
OK, I will bookmark these various issues, and if I ever get a sensible amount of free time I will investigate the various other options. Even the worst case of using the static binaries shouldn't be the end of the world, I doubt the shared binaries end up sharing significantly sized libraries with other processes, and with no long-running daemon memory spikes should be limited to container (re)start. |
|
Hey everyone! I am getting the same issue on 20.04lts. I am fairly new to this whole thing, so if anyone could give me instruction on "how to get the debs" It would be greatly appreciated. I can get the tar.gz from the repo by putting the url http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/ in the browser but not really sure if that is what i need to do, or how to proceed from there. Can someone help me out with the "for dummies" version of a workaround. Thanks in advance |
I have reverted my decision mentioned in #14278 (comment) 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. |
@lsm5 Will this be reverted in kubic for xUbuntu_18.04 as well (https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04/) ? |
Yes, i'm fixing that up right now. There should be a build in sometime. |
18.04 should be fixed now. Let me know if any issues. |
@lsm5 Now I see this error when trying to install from https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04/
|
@lsm5 I think initially podman version was 3.0.1 here : https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04/ but you have reverted bit higher version (3.4.2) which might be causing this dependency error above ? Can you please revert back the version which was existing earlier ? |
@ppadashe i've fixed the dependencies. Please try again. |
Podman install is going through now but I see following error post that on doing Podman login to image registry
How can this be fixed? |
@rachnajain-ibm is this on 22.04 ? If it's on 18.04, can you try in rootful mode? |
This is on 18.04
Why rootful mode is required now? |
let me see if i can fix that. |
@lsm5 : We are also blocked by the same error reported . Can you help us to get unblocked and proceed ?
|
working on it, will update here once it's done. |
@rachnajain-ibm @rayankiy rootless should be fixed now, please refresh your repos and try again. Thanks. |
By default it does not work, we need a working default one on ubuntu 18.04
|
@lospringliu can you confirm you have:
I have these on my 18.04 instance with the Kubic repo and the command you gave works for me. |
@lsm5 : Still failing with
|
@lsm5 , actually there is no I think there is differences when users use different mirrors |
@lospringliu mirror syncing may take a while I guess. @rayankiy do you have those podman and fuse-overlayfs packages I posted in the earlier comment? |
it replaces fuse with fuse3, which is not as clean as podman v3.0.1
|
@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. |
understand and thanks, it works anyway with warnings |
It is still not working getting same error.
|
@rachnajain-ibm Try to install podman with --install-recommends option. Something like this
|
thanks @lsm5 , work for me with the 18.04 repo and install with the |
@lsm5, Looks like the mirror is out of sync again.
Ubuntu2004:
|
let me see if i can fix it quick. @containers/podman-maintainers i wonder if this is a burden we have to live with for the lifetime of ubuntu 18.04 and ubuntu 20.04. I gotta check with the openbuildservice people why this happens frequently. |
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. |
|
@lsm5 - Now working. Thank you very, very much! I appreciate you. |
@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've rather lost track of where we are with this, but the Ubuntu 20.04 and 22.04 arm64 repos seem to be broken - not sure if they're supposed to be working or not at this point! |
@srd424 Can you let me know which exact repo you are trying to use for each and also the error messages you see? Ubuntu 22.04 has packages in its default repo itself, so if you're using it in production, please use only the official Ubuntu packages. |
Pardon the necro but you can install Podman 4.1.1 on Ubuntu 22.04 by using the alvistack repo. wget https://downloadcontent.opensuse.org/repositories/home:alvistack/xUbuntu_22.04/Release.key -O alvistack_key
gpg --dearmor < alvistack_key | sudo tee /etc/apt/trusted.gpg.d/alvistack.gpg >/dev/null
echo "deb https://downloadcontent.opensuse.org/repositories/home:alvistack/xUbuntu_22.04/ /" | sudo tee /etc/apt/sources.list.d/alvistack.list
sudo apt update
sudo apt upgrade
sudo apt install podman python3-podman-compose |
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:
Describe the results you received:
Podman installation fails with error:
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: cri-o/cri-o#5802
Output of
podman version
:N/A - podman cannot be installed
Package info (e.g. output of
rpm -q podman
orapt list podman
):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:
The text was updated successfully, but these errors were encountered: