podman: apt update errors out on https redirect on 22.04.3
Issue Description
I have a local installation following the official instructions for Ubuntu 22.04: https://podman.io/docs/installation
Lately, I saw that apt complains about the redirect for the podman source:
Ign:5 https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Unstable InRelease
Err:6 https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Unstable Release
Redirection from https to 'http://download.opensuse.org/repositories/devel:kubic:libcontainers:/unstable/Debian_Unstable/Release' is forbidden [IP: 195.135.223.226 443]
Reading package lists... Done
E: The repository 'https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Unstable Release' does not have a Release file.
Steps to reproduce the issue
Steps to reproduce the issue
- run a ubunt:22.04 container
- follow Debian install steps in https://podman.io/docs/installation
apt update
Describe the results you received
apt update fails for the podman source.
Describe the results you expected
apt update should work using the podman source. installation steps should work on 22.04
podman info output
The issue affects installing podman.
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Reactions: 1
- Comments: 21 (4 by maintainers)
Please don’t downgrade to HTTP, that’s not a valuable workaround for security reasons.
Everyone,
The issue should be resolved now.
Please verify that the HTTPS works correctly for you - both the main repository URL and the local mirrors (where the requests would be redirected to) should be using HTTPS endpoints now.
I also encourage everyone who eagerly went ahead and made updates to use plain HTTP to revert the changes back to use HTTPS, if possible.
@lsm5
First of all thank you for maintaining the unstable repos up until now. 🙏
For Debian/Ubuntu users can you recommend alternative repos ?
Okay, I got it working by doing just one thing
within my installation script I’ve changed the below part
to below one (note the https -> http)
So, my cautious suggestion for those who try to update CRIO, please try changing the protocol specified in files within /etc/apt/sources.list.d/ directory and then see what happens