Closed ahromis closed 8 months ago
This has been fixed in our dev branch. Adding a call to apt-get update before the call to install curl will work.
I noticed this had been closed, but I've done as suggested (adding 'apt-get update' before the call) but getting similar outcome:
app/server# apt update && apt install curl
Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Err:4 http://archive.ubuntu.com/ubuntu jammy Release
404 File not found [IP: 91.189.91.83 80]
Ign:5 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:6 https://ppa.launchpadcontent.net/deadsnakes/ppa/ubuntu jammy InRelease
Err:7 http://archive.ubuntu.com/ubuntu jammy-updates Release
404 File not found [IP: 91.189.91.83 80]
Err:8 http://security.ubuntu.com/ubuntu jammy-security Release
404 File not found [IP: 91.189.91.82 80]
Err:9 http://archive.ubuntu.com/ubuntu jammy-backports Release
404 File not found [IP: 91.189.91.83 80]
Ign:10 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Ign:6 https://ppa.launchpadcontent.net/deadsnakes/ppa/ubuntu jammy InRelease
Ign:10 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Ign:6 https://ppa.launchpadcontent.net/deadsnakes/ppa/ubuntu jammy InRelease
Ign:10 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Err:6 https://ppa.launchpadcontent.net/deadsnakes/ppa/ubuntu jammy InRelease
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 185.125.190.52 443]
Err:10 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 13.80.99.124 443]
Reading package lists... Done
E: The repository 'http://archive.ubuntu.com/ubuntu jammy Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
This is using the latest image (:latest)
Area of Concern
Describe the bug A clear and concise description of what the bug is.
When installing images through the container image I think it needs to run
apt-get update
first. I was getting the following error when installing a module through the UI:When exec'd into the container and ran
apt-get update
first then the modules could install.Expected behavior A clear and concise description of what you expected to happen.
The module to install without errors.
Screenshots If applicable, add screenshots to help explain your problem.
More details:
Your System (please complete the following information):
Additional context Add any other context about the problem here.