You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we do an umoci unpack we currently only keep track of the manifest hash that we extracted. We should also save (in umoci.state or something) the name of the reference that we dereferenced in order to get the extracted rootfs. This will allow us to remove the tedious --from argument in umoci repack.
The only real question to ask is whether we should make it possible for someone to forcefully create a rootfs that we cannot be sure is valid (namely specify --from and --mtree manually).
The text was updated successfully, but these errors were encountered:
When we do an
umoci unpack
we currently only keep track of the manifest hash that we extracted. We should also save (inumoci.state
or something) the name of the reference that we dereferenced in order to get the extracted rootfs. This will allow us to remove the tedious--from
argument inumoci repack
.The only real question to ask is whether we should make it possible for someone to forcefully create a rootfs that we cannot be sure is valid (namely specify
--from
and--mtree
manually).The text was updated successfully, but these errors were encountered: