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.

Sign up for GitHub

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

Jump to bottom

Fresh project setup fails because of out of support base operating system #1869

Closed
6 of 7 tasks
biggianteye opened this issue Jun 29, 2023 · 3 comments
Closed
6 of 7 tasks

Fresh project setup fails because of out of support base operating system #1869

biggianteye opened this issue Jun 29, 2023 · 3 comments
Assignees
@gnclmorais

Comments

@biggianteye
Copy link
Contributor

biggianteye commented Jun 29, 2023 •
edited by gnclmorais
Loading

Description of the issue 📄

When trying to run ./bin/dbuild in a freshly checked out repo, it fails with this error:

failed to solve: process "/bin/sh -c curl -sL https://deb.nodesource.com/setup_12.x | bash -" did not complete successfully: exit code: 1

There is a deprecation warning about Node 12 earlier on in the output but this is a red herring. The problem arises from the fact that the node installation script first tries to update the list of available operating system packages.

Error output 
#0 20.26 ## Installing the NodeSource Node.js 12.x repo...
#0 20.26
#0 20.27
#0 20.27 ## Populating apt-get cache...
#0 20.27
#0 20.27 + apt-get update
#0 22.52 Ign http://security.debian.org jessie/updates InRelease
#0 22.52 Ign http://deb.debian.org jessie InRelease
#0 22.54 Ign http://security.debian.org jessie/updates Release.gpg
#0 22.57 Ign http://security.debian.org jessie/updates Release
#0 22.57 Ign http://deb.debian.org jessie-updates InRelease
#0 22.61 Ign http://deb.debian.org jessie Release.gpg
#0 22.63 Err http://security.debian.org jessie/updates/main arm64 Packages
#0 22.63
#0 22.66 Ign http://deb.debian.org jessie-updates Release.gpg
#0 22.67 Err http://security.debian.org jessie/updates/main arm64 Packages
#0 22.67
#0 22.68 Ign http://deb.debian.org jessie Release
#0 22.71 Ign http://deb.debian.org jessie-updates Release
#0 22.71 Err http://security.debian.org jessie/updates/main arm64 Packages
#0 22.71
#0 22.76 Err http://security.debian.org jessie/updates/main arm64 Packages
#0 22.76
#0 22.80 Err http://security.debian.org jessie/updates/main arm64 Packages
#0 22.80   404  Not Found [IP: 151.101.66.132 80]
#0 23.50 Err http://deb.debian.org jessie/main arm64 Packages
#0 23.50   404  Not Found
#0 23.60 Err http://deb.debian.org jessie-updates/main arm64 Packages
#0 23.60   404  Not Found
#0 23.61 W: Failed to fetch http://security.debian.org/dists/jessie/updates/main/binary-arm64/Packages  404  Not Found [IP: 151.101.66.132 80]
#0 23.61
#0 23.61 W: Failed to fetch http://deb.debian.org/debian/dists/jessie/main/binary-arm64/Packages  404  Not Found
#0 23.61
#0 23.61 W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-arm64/Packages  404  Not Found
#0 23.61
#0 23.61 E: Some index files failed to download. They have been ignored, or old ones used instead.
#0 23.61 Error executing command, exiting
------
failed to solve: process "/bin/sh -c curl -sL https://deb.nodesource.com/setup_12.x | bash -" did not complete successfully: exit code: 1

The docker image used by the project is built on top of the ruby:2.4.2 image which is now 6 years old. This uses Debian Jessie which reached end of Long Term Support in June 2020 and now the package repositories return a 404 as seen in the output above.

This is not a good experience for anyone new wanting to contribute to the project.

Screenshots 📷

n/a

Steps to fix 🛠

The fix would be to upgrade the base operating system. I don't know what the project's needs are in terms of Ruby versions and underlying operating system, but here are some options:

According to the Debian releases page:

  • Debian 11 (bullseye) — current oldstable release
  • Debian 10 (buster) — current oldoldstable release, under LTS support

If there is going to be effort spent on upgrading, it would be worth spending it on something more recent than those options.

To do 📋

  • Claim this issue (comment below, or assign yourself if you are part of the codebar org)
  • Fork and clone the repository
  • Update the relevant files. Follow the steps to fix section in this issue.
  • Commit your changes as one commit. Use the title of this issue as your commit message
  • Submit a pull request
  • Mention this issue in the PR description by including it's number
  • Have your pull request reviewed & merged by a codebar team member
@biggianteye
Copy link
Contributor Author

I bumped up the docker image to ruby:2.4.10 and the build succeeded. Though as mentioned, this is a temporary measure rather than a proper fix.

There were a couple of test failures like this one but I suspect they are transient problems unrelated to the version bump.

1) Admin managing members Admin managing members can unsubscribe a member from group
Failure/Error: visit admin_member_path(member)

Selenium::WebDriver::Error::UnknownError:
  unknown error: Chrome failed to start: crashed.
    (chrome not reachable)
    (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)

gnclmorais added a commit to gnclmorais/planner that referenced this issue Jul 15, 2023
@gnclmorais
Update Dockerfile (and Ruby version)
5dd7abf 
@biggianteye pointed out to us that our Docker instructions were
no longer up to date, running into a few issues while trying to
set the website up using them. This commit updates the Ruby version
slightly so that we can use another Docker image as a base.

Fixes codebar#1869
@gnclmorais gnclmorais mentioned this issue Jul 15, 2023
Closed
gnclmorais added a commit to gnclmorais/planner that referenced this issue Jul 15, 2023
@gnclmorais
Update Dockerfile (and Ruby version)
61cb8e4 
@biggianteye pointed out to us that our Docker instructions were
no longer up to date, running into a few issues while trying to
set the website up using them. This commit updates the Ruby version
slightly so that we can use another Docker image as a base.

Fixes codebar#1869
@gnclmorais
Copy link
Contributor

gnclmorais commented Jul 15, 2023 •
edited
Loading

I think I was able to (temporarily) solve this at #1874. Thank you @biggianteye for bringing this to our attention!

@gnclmorais gnclmorais self-assigned this Jul 16, 2023
gnclmorais added a commit to gnclmorais/planner that referenced this issue Jul 17, 2023
@gnclmorais
Update Dockerfile (and Ruby version)
e2f4ce8 
@biggianteye pointed out to us that our Docker instructions were
no longer up to date, running into a few issues while trying to
set the website up using them. This commit updates the Ruby version
slightly so that we can use another Docker image as a base.

Fixes codebar#1869
@gnclmorais
Copy link
Contributor

I worked on this #1874, but it seems @asideofcode-dev fixed it marvellously as a consequence with #1882! Great job :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gnclmorais gnclmorais

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update Dockerfile (and Ruby version) gnclmorais/planner
2 participants
@gnclmorais @biggianteye