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

Scaphandre docker image uses deprecated ubuntu version which prevents update #150

Closed
demeringo opened this issue Jan 5, 2022 · 3 comments · Fixed by #151
Closed

Scaphandre docker image uses deprecated ubuntu version which prevents update #150

demeringo opened this issue Jan 5, 2022 · 3 comments · Fixed by #151
Labels
bug Something isn't working
Projects

Comments

@demeringo
Copy link
Contributor

Bug description

hubblo/scaphandre container image is based on ubuntu 20.10 (a non LTS and now unsupported version).

Following deprecation of the ubuntu repositories, I cannot install additional software in the container.

apt update from inside the container returns

E: The repository 'http://archive.ubuntu.com/ubuntu groovy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

or local docker build (docker build .) fails for similar reason.

To Reproduce

  1. sudo docker run -it --entrypoint /bin/sh hubblo/scaphandre:latest
  2. inside container cat /etc/issue returns Ubuntu 20.10 \n \l
  3. inside container apt update returns errors:
Ign:1 http://archive.ubuntu.com/ubuntu groovy InRelease
Ign:2 http://archive.ubuntu.com/ubuntu groovy-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu groovy-backports InRelease
Err:4 http://archive.ubuntu.com/ubuntu groovy Release
  404  Not Found [IP: 91.189.88.142 80]
Err:5 http://archive.ubuntu.com/ubuntu groovy-updates Release
  404  Not Found [IP: 91.189.88.142 80]
Err:6 http://archive.ubuntu.com/ubuntu groovy-backports Release
  404  Not Found [IP: 91.189.88.142 80]
Ign:7 http://security.ubuntu.com/ubuntu groovy-security InRelease
Err:8 http://security.ubuntu.com/ubuntu groovy-security Release
  404  Not Found [IP: 91.189.91.39 80]
Reading package lists... Done
E: The repository 'http://archive.ubuntu.com/ubuntu groovy Release' does not have 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 groovy-updates Release' does not have 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 groovy-backports Release' does not have 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 groovy-security Release' does not have 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.

Expected behavior

Update Dockerfile (line 27) to use a supported Ubuntu version, either:

  • an older LTS version (20.04)
  • latest interim release (21.10)

Rebuid and publish updated image to docker hub as hubblo/scaphandre:latest

Screenshots

N/A

Environment

N/A

Additional context

@demeringo demeringo added the bug Something isn't working label Jan 5, 2022
@bpetit bpetit added this to Triage in General Jan 6, 2022
@bpetit bpetit linked a pull request Jan 6, 2022 that will close this issue
@bpetit
Copy link
Contributor

bpetit commented Jan 6, 2022

Your fix to run on 20.04 seems like the best choice. Thanks for that !

@bpetit bpetit moved this from Triage to To do in General Jan 6, 2022
@demeringo
Copy link
Contributor Author

demeringo commented Jan 29, 2022

hi @bpetit

  • should I close this issue now, on the rationale that the PR has been merged to dev ?
    or
  • should we rather close it only after this has been integrated to next release ?

And a related question is: when should we republish the docker image ?

This last question of managing the update of the docker image is also linked to #152 opened by @rossf7 (it would add the ability to automate the publication of not-yet-stable (dev-based) images in addition to the stable releases).
=> it may be easier to integrate #152 first.

@bpetit
Copy link
Contributor

bpetit commented Jun 15, 2022

I'll close it now, the release is close.

Having tagged versions according to git tags (ie releases), on one side, and a :dev image that's close to the latest code in dev, is fine for me.

@bpetit bpetit closed this as completed Jun 15, 2022
General automation moved this from To do to Done Jun 15, 2022
@bpetit bpetit moved this from Done to Previous releases in General Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
General
Previous releases
Development

Successfully merging a pull request may close this issue.

2 participants