Conversation
Madhunika-atmakuri
approved these changes
Oct 29, 2025
|
dgburr
added a commit
that referenced
this pull request
Oct 30, 2025
Update the docker build image to fix the "Generate artifacts" step after the changes to the docker file in #1520
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The Ubuntu deadsnakes PPA dropped support for Focal Fossa (20.04.6 LTS) on the 1st of October (see deadsnakes/py3.11@54c42ed). Therefore the current docker image can no longer be rebuilt. This PR updates the docker image as follows:
Note that the "Build Docker Image" step will not pass until #1521 is merged.
API compatibility
Does this change introduce a API compatibility risk?
No, although this may impact customers in the future if they have older build toolchains and we start making use of features not available in gcc 7.
API compatibility plan
If the above is "Yes", please detail the compatibility (or migration) plan:
N/A
JIRA Reference
https://swift-nav.atlassian.net/browse/BOARD-XXXX