-
Notifications
You must be signed in to change notification settings - Fork 11
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
fix: proper usage of ostree container commit
#101
Comments
So to do this would require some changes to the |
The cache shouldn't be in the image, |
After some testing it wouldn't work with our config and module mounts either. We can either make use of a |
NVM this seems to indicate that having an |
Actually it seems that using mounts is supported! https://github.com/ostreedev/ostree-rs-ext/blob/main/lib/src/commit.rs#L63 Also local testing seems to work with putting |
I was just reading the CoreOS documentation on OSTree Native Containers and saw this:
We should remove the additional
RUN ostree container commit
step, and instead add it to the end of eachRUN
command.This was not an issue previously with the legacy template, as all the modules were run as a single layer.
Read more: ostreedev/ostree-rs-ext#159
The text was updated successfully, but these errors were encountered: