-
Notifications
You must be signed in to change notification settings - Fork 79
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
tracker: bootc container storage #721
Labels
Comments
cgwalters
added
enhancement
New feature or request
area/client
Related to the client/CLI
labels
Jul 23, 2024
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 24, 2024
WIP for containers#721 Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 25, 2024
WIP for containers#721 Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 25, 2024
Prep for containers#721 Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 25, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 27, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 28, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 28, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 29, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 29, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 30, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 30, 2024
Initial work for: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - "Open" it (but do nothing with it) as part of the core CLI operations Further APIs and work will build on top of this. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 30, 2024
Closes: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - Open it at the same time we open the ostree repo/sysroot - Change bound images to use this We are *NOT* yet changing the base bootc image pull to use this. That's an obvious next step (xref containers#215 ) but will come later. Signed-off-by: Colin Walters <[email protected]>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Jul 31, 2024
Closes: containers#721 - Initialize a containers-storage: instance at install time (that defaults to empty) - Open it at the same time we open the ostree repo/sysroot - Change bound images to use this We are *NOT* yet changing the base bootc image pull to use this. That's an obvious next step (xref containers#215 ) but will come later. Signed-off-by: Colin Walters <[email protected]>
Open
cgwalters
pushed a commit
to cgwalters/bootc
that referenced
this issue
Nov 5, 2024
….5.17 build(deps): bump clap from 4.5.16 to 4.5.17
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of both logically bound images as well as migrating to a containers-image/storage backend we should actually as a preparatory step introduce the "bootc container storage".
Current architecture
Looking at a physical bootc-installed filesystem basically all content is underneath
/ostree
, and the content managed by bootc itself is mostly under/ostree/repo
. I think we should introduce/ostree/bootc
as its own dedicated directory.Support usage from podman
We could have a symlink inside the booted root as
/usr/lib/bootc/storage-root
or so that would point to/sysroot/ostree/bootc
. Then, users of logically bound images would either need to explicitly configure that as--root
, or possibly we encourage configuring the podman stack to use this as an additional store.The text was updated successfully, but these errors were encountered: