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
ci: always pull docker image from remote to prevent out of sync tags #12351
ci: always pull docker image from remote to prevent out of sync tags #12351
Conversation
... to prevent out of sync tags Signed-off-by: Fritz Lehnert <13189449+Neudrino@users.noreply.github.com>
Thanks for opening a PR! 💯
Howto
More infoPlease take a moment to read through the Magma project's
If this is your first Magma PR, also consider reading
|
Signed-off-by: Fritz Lehnert <13189449+Neudrino@users.noreply.github.com>
Looks like the OWNERS masks are confusing this GitHub workflow for a bazel BUILD file? Hence the review is only |
…ulling Signed-off-by: Fritz Lehnert <13189449+Neudrino@users.noreply.github.com>
5eb376d
to
c99eb89
Compare
Tested extensively on #12271. Image was updated correctly 👍 . We should track somewhere that this should be changed for all workflows that use the latest devcontainer image. |
This file was added on purpose to |
…agma#12351) * ci: always pull docker image from remote ... to prevent out of sync tags Signed-off-by: Fritz Lehnert <13189449+Neudrino@users.noreply.github.com> * ci: update docker action to v3 Signed-off-by: Fritz Lehnert <13189449+Neudrino@users.noreply.github.com> * ci: ensure the devcontainer latest tag is up to date locally before pulling Signed-off-by: Fritz Lehnert <13189449+Neudrino@users.noreply.github.com>
Summary
Github action runners are not managed by Magma and might be reused several times. The docker documentation seems to suggest, that if a image is already present in the local docker registry, it will not be re-fetched from the remote unless explicitly told so. See the option
--pull
with defaultmissing
in the docker documentation. This can lead to stale images being used.To mitigate the issue we need to force pull the first time we use an image within the workflow.
Keep in mind that we do not want to force pull in every following action as this would bring the risk to use different images in one workflow run, when a image tag is updated during that workflow run.
The
addnab/docker-run-action
required an update to versionv3
for this to work.Test Plan
Additional Information