Skip to content
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.

support injecting additional content (rpms) #23

Closed
cgwalters opened this issue Apr 29, 2021 · 2 comments
Closed

support injecting additional content (rpms) #23

cgwalters opened this issue Apr 29, 2021 · 2 comments

Comments

@cgwalters
Copy link
Member

In order to support replacing cosa upload-oscontainer functionality, we need to at least support generating something that looks like the RHCOS machine-os-content today which has both an ostree commit as well as a set of "extension" RPMs.

Something like:

$ ostree-ext-cli container export --add /path/to/dir:/srv/extensions --repo=tmp/repo ...

Where /path/to/dir has a directory with rpms.
@cgwalters cgwalters mentioned this issue Apr 29, 2021
Closed
cgwalters added a commit to cgwalters/os that referenced this issue Jul 26, 2021
@cgwalters
image: Switch to ostree-format: oci
8e0a9d2 
This is the RHCOS version of coreos/fedora-coreos-config#1097

I was hoping to land this in FCOS first but I'm kind of blocked
on that in coreos/fedora-coreos-pipeline#359, so
let's settle for parallel.

NOTE!  This **does not change** the effect of `cosa upload-oscontainer` etc.
Some discussion on that here:
ostreedev/ostree-rs-ext#23
and I will file more issues related to that.

However, what this *will* do is allow us to push this *additional* image
arounnd and make `podman run registry.ci.openshift.org/rhcos/rhcos:4.8` e.g.
work.  In other words to start this will just be something *we* use
to quickly inspect rhcos-as-container, not something we actually ship.
(OK that's kind of a lie, it will end up in a place like e.g.
 http://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/4.9.0-0.nightly-2021-07-20-014024/
 instead of the existing `ostree.tar` so in theory other people outside
 of our group could run it too, but 🤫)
@cgwalters cgwalters mentioned this issue Jul 26, 2021
Merged
cgwalters added a commit to cgwalters/os that referenced this issue Aug 30, 2021
@cgwalters
image: Switch to ostree-format: oci
7a4d1bc 
This is the RHCOS version of coreos/fedora-coreos-config#1097

I was hoping to land this in FCOS first but I'm kind of blocked
on that in coreos/fedora-coreos-pipeline#359, so
let's settle for parallel.

NOTE!  This **does not change** the effect of `cosa upload-oscontainer` etc.
Some discussion on that here:
ostreedev/ostree-rs-ext#23
and I will file more issues related to that.

However, what this *will* do is allow us to push this *additional* image
arounnd and make `podman run registry.ci.openshift.org/rhcos/rhcos:4.8` e.g.
work.  In other words to start this will just be something *we* use
to quickly inspect rhcos-as-container, not something we actually ship.
(OK that's kind of a lie, it will end up in a place like e.g.
 http://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/4.9.0-0.nightly-2021-07-20-014024/
 instead of the existing `ostree.tar` so in theory other people outside
 of our group could run it too, but 🤫)
@cgwalters cgwalters mentioned this issue Aug 30, 2021
Merged
@cgwalters
Copy link
Member Author

This also relates to #12
except here what we want is a place to put additional stuff that shouldn't be part of the on-disk ostree.

Perhaps it's logically cleanest if e.g. in OpenShift we actually ship two images machine-os-content and machine-os-extensions - the latter can derive from the first, but we only pull the latter when desired?

cgwalters added a commit to cgwalters/os that referenced this issue Sep 8, 2021
@cgwalters
image: Switch to ostree-format: oci
4d62fea 
This is the RHCOS version of coreos/fedora-coreos-config#1097

I was hoping to land this in FCOS first but I'm kind of blocked
on that in coreos/fedora-coreos-pipeline#359, so
let's settle for parallel.

NOTE!  This **does not change** the effect of `cosa upload-oscontainer` etc.
Some discussion on that here:
ostreedev/ostree-rs-ext#23
and I will file more issues related to that.

However, what this *will* do is allow us to push this *additional* image
arounnd and make `podman run registry.ci.openshift.org/rhcos/rhcos:4.8` e.g.
work.  In other words to start this will just be something *we* use
to quickly inspect rhcos-as-container, not something we actually ship.
(OK that's kind of a lie, it will end up in a place like e.g.
 http://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/4.9.0-0.nightly-2021-07-20-014024/
 instead of the existing `ostree.tar` so in theory other people outside
 of our group could run it too, but 🤫)
@cgwalters cgwalters mentioned this issue Sep 8, 2021
Merged
@cgwalters
Copy link
Member Author

I think this should be instead #12

ravanelli pushed a commit to ravanelli/os that referenced this issue Oct 5, 2021
@cgwalters @ravanelli
image: Switch to ostree-format: oci
05f137a 
This is the RHCOS version of coreos/fedora-coreos-config#1097

I was hoping to land this in FCOS first but I'm kind of blocked
on that in coreos/fedora-coreos-pipeline#359, so
let's settle for parallel.

NOTE!  This **does not change** the effect of `cosa upload-oscontainer` etc.
Some discussion on that here:
ostreedev/ostree-rs-ext#23
and I will file more issues related to that.

However, what this *will* do is allow us to push this *additional* image
arounnd and make `podman run registry.ci.openshift.org/rhcos/rhcos:4.8` e.g.
work.  In other words to start this will just be something *we* use
to quickly inspect rhcos-as-container, not something we actually ship.
(OK that's kind of a lie, it will end up in a place like e.g.
 http://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/4.9.0-0.nightly-2021-07-20-014024/
 instead of the existing `ostree.tar` so in theory other people outside
 of our group could run it too, but 🤫)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cgwalters