Skip to content
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

Add ex deploy-from-self #3961

Merged
merged 1 commit into from
Aug 26, 2022
Merged

Conversation

cgwalters
Copy link
Member

This experimental command is intended to be mainly used in OCP
where we're trying to do a cutover to the new format container images.
However, we have the problem of old disk images where the rpm-ostree
there is too old to understand the container bits. (Not to mention
skopeo is too old)

This code (+ integration test) demonstrates running the new OS
update as a privileged container which mounts the host filesystem
and performs the update that way.

A downside of this is that we only write the raw ostree commit;
we don't write the container-ostree refs; in other words, the
next update will need to re-pull the container. That's...fixable,
it just requires a bit more nontrivial work that we can do later
as an optimization.

@cgwalters cgwalters force-pushed the ex-inplace-container-deploy branch 2 times, most recently from 6bb7086 to e6b6cf8 Compare August 24, 2022 22:44
This experimental command is intended to be mainly used in OCP
where we're trying to do a cutover to the new format container images.
However, we have the problem of old disk images where the rpm-ostree
there is too old to understand the container bits.  (Not to mention
skopeo is too old)

This code (+ integration test) demonstrates running the new OS
update *as a privileged container* which mounts the host filesystem
and performs the update that way.

A downside of this is that we only write the raw ostree commit;
we don't write the container-ostree refs; in other words, the
next update will need to re-pull the container.  That's...fixable,
it just requires a bit more nontrivial work that we can do later
as an optimization.
@cgwalters
Copy link
Member Author

Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

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

lgtm, pretty cool stuff here!

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

Successfully merging this pull request may close these issues.

2 participants