#4143 new task

Refresh docker builder images

Reported by: btlogy Owned by: btlogy
Priority: normal Milestone: undecided
Component: dev-infrastructure Version: n/a
Keywords: Cc:
Launchpad Bug:

Description (last modified by btlogy)

We have a couple of opened tickets which requires new/updated docker images:

  • #4131 needs an update of oraclelinux-8 to phase out python to 3.8 (EOL)
  • #4137 needs a new fedora-41 images to phase out fedora-35 (EOL)

I think it also makes sense to prepare new images to start building/testing on:

  • debian-12 before phasing out debian-11
  • ubuntu-24.04 before phasing out ubuntu-20.04
  • oraclelinux-9 before phasing out oraclelinux-8

I propose to PR the addition/update of those new images in the images workflow first, so we can phase the older ones in the ci workflow later.

Change History (4)

comment:1 Changed at 2024-12-10T11:17:15Z by btlogy

  • Owner set to btlogy

comment:2 Changed at 2024-12-10T17:47:39Z by btlogy

  • Description modified (diff)

comment:3 Changed at 2024-12-10T20:39:59Z by btlogy

As discussed in the N&B this Tue 10 of Dec., we're going to try to build those images with Meejah special admin user.

Step to proceed:

  1. btlogy will submit a PR changing only the images workflow: PR#1409
  2. meejah will have to login with the admin user on CircleCI login-public
  3. meejah will have to either manually trigger the build on the pull/1409 branch reversing the 2 options (build-images=true, run-tests=false), or generate a token to use the .circleci/rebuild-images.sh script locally.

WARN: We might have to merge this PR before step 3 and trigger the build on the master branch instead.

If that fail, we might have to bypass the push/pull of those custom images by building directly from the upstream each time (which will likely take a bit more time per run - yet to be measure).

comment:4 Changed at 2024-12-10T20:48:48Z by meejah

Job was rejected because this version of Docker is not supported on this resource class. Try removing the version of Docker in your .circleci/config.yml and re-running

Note: See TracTickets for help on using tickets.