-
Notifications
You must be signed in to change notification settings - Fork 542
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
RFC: crane mutate to modify image metadata #281
Comments
I want it still. |
How's this for a fairly minimal first stab:
For wdyt? |
Agree for
Ok with it for now, but leave a TODO. We should support this. Let's land at least |
Yeah, I want I want |
This would surprise me as default behavior. How would you feel about a |
I'd be okay with that. |
@squee1945 mentioned it might be useful to have a tool that can change the entrypoint in an image in a registry in one command. Remotely adding/removing envs and labels seems useful too, and would be done nearly exactly the same way.
Strawman usage
This would fetch the config for the image, update entrypoint/env/labels, and push a new manifest with the original image's layers and the modified config. No layers would be copied, and the new image would be pushed to the original image's repository.
From there, you can tag the resulting digest with
crane cp <digest> <tag-you-want>
(sidenote: maybecrane tag
would be a useful alias?)Alternatives considered
We could have separate commands that would each do one operation, e.g.:
You get the idea. Since the output is the new digest, you could theoretically chain them:
But that's gross, and also ends up sending multiple updates needlessly. So let's not do that.
The text was updated successfully, but these errors were encountered: