Actions
Support #22693
closed
Update Docker pin to Docker 28
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Due date:
Story points:
-
Description
This version came out while 3.1.0 was being released. We should test that all our components work with it, then update the pin accordingly.
- Make a branch that updates the pin.
- Build a new Jenkins test image from that branch.
- Run tests on that new image.
- If there are any failures, file bugs and address those.
- Once all tests are passing, merge the branch with the new pin to main.
Updated by Brett Smith 10 days ago
22693-docker-28 @ 4b086b81ca6f3f2d00c4e25060d76729bbedeaa9
Image build: packer-build-jenkins-image-arvados-tests: #118
Test run: developer-run-tests: #4709
You can confirm from console output in the test run that the pin took as expected:
singularity: singularity-ce version 3.10.4 docker client: Docker version 28.0.2, build 0442a73 docker server: 28.0.2 R: /usr/bin/Rscript
If you are wondering why I didn't also change the containerd pin: they're on completely separate release cycles, 1.17 is still the latest.
- All agreed upon points are implemented / addressed.
- Yes
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- N/A
- Code is tested and passing, both automated and manual, what manual testing was done is described
- See above
- Documentation has been updated.
- N/A
- Behaves appropriately at the intended scale (describe intended scale).
- No change
- Considered backwards and forwards compatibility issues between client and server.
- N/A
- Follows our coding standards and GUI style guidelines.
- It is literally a one-character change
Updated by Lucas Di Pentima 10 days ago
Everything looks good, please merge. Thanks!
Updated by Brett Smith 10 days ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|41cbe54d0c85d2f8b615d1df91479537c6bfac72.
Actions