feat(docker/build-push): read truenas oci registry from vault - #28
Merged
Conversation
Contributor
Author
|
@chjdev I changed CI to run on github runners since public repo CI does not run on self-hosted (which makes sense security wise). |
ci: test running on gh hosted runners
antholzer
force-pushed
the
feat/truenas-registry-from-vault
branch
from
September 2, 2026 11:16
ab5d29d to
82783f0
Compare
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.
So that we no longer need to add them in each runner and we now have a login step in both cases (ghcr and truenas).