A Composite Github Action that eases the usage of google/go-containerregistry in your project
- See the sample test.yaml on usage.
- Basically
- id: crane-setup
uses: comdotlinux/crane@v1.0.0
- run: $CRANE
env:
CRANE: ${{ steps.crane-setup.outputs.crane-path }}- https://github.com/google/go-containerregistry has some interesting things to use (See Readme for usage)
- After using this action you should have a crane command available for you to use installed for that github workflow.
- Mostly when workign with different remote docker registries, it is difficult to move docker images between two registries.
- When docker image registries are separated fro dev and prod, you need to move the docker image before the deployment.
- When using the default docker commandline, the only way to do this is
- Pull the docker image
- Tag the local docker image with the name of the destination docker image registry
- Push the new docker image
- This is fine but wastes time and network resources, as we cannot benefit from the docker layer caching becuase before pushing (i.e. when pulling) you cannot know if any layers exist in the desination.
- See the Issues / Milestones