Skip to content
This repository has been archived by the owner on Jan 15, 2025. It is now read-only.

container/deploy: Add a --target-imgref option #135

Merged
merged 1 commit into from
Oct 29, 2021

Conversation

cgwalters
Copy link
Member

We want the ability to separate the image that's pulled from its
target reference. This is what we do today in coreos-assembler
for pure ostree refs - e.g. we deploy via a commit hash, but
still have ostree admin upgrade pull from a ref.

This is equivalent functionality for containers.

We want the ability to separate the image that's pulled from its
target reference.  This is what we do today in coreos-assembler
for pure ostree refs - e.g. we deploy via a commit hash, but
still have `ostree admin upgrade` pull from a ref.

This is equivalent functionality for containers.
/// If specified, `--imgref` will be used as a source, but this reference will be emitted into the origin
/// so that later OS updates pull from it.
#[structopt(long)]
target_imgref: Option<String>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess longer term we'd need to find a better term for this, because I think many people will fall in this pinned-digest vs moveable-tag trap (and I'm still sad we can't use the digest-and-tag form).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least in coreos-assembler right now, we're pulling via oci-archive over 9p from the build directory, so the image references look completely different.

But other workflows indeed may want to push to a registry, in which case having a separate --digest argument would make sense.

@cgwalters cgwalters merged commit 2fb4732 into ostreedev:main Oct 29, 2021
@cgwalters
Copy link
Member Author

Followup #144

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants