CASMINST-4471 simplify build and properly load nexus images with new podman #6
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.
Signed-off-by: Jacob Salmela [email protected]
Summary and Scope
podman load
no longer accepts a name and tag. Instead you must load the image, and then run a separatepodman tag
command.podman inspect
also needed the--type container
flag, otherwise it was causing false logic by hitting a match since it can match anything that matches that name without a--type
flag.This also finds the image ID in a more reliable manner, by checking it's metadata for a label:
Issues and Related PRs
Testing
Removed the existing pit-nexus rpm, installed the one from the build.
Validated nexus was running, the pods were started and the volumes were created.
Stopped the service, restarted it.
Tested on:
#redbull
Risks and Mitigations
Low, still broken.
Pull Request Checklist