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
Right now, if I want to use the containers-storage CLI tool to mount an image so I can explore its filesystem (without creating a container), I seem to have to:
run containers-storage image myimagename
take the "Top layer" id from its output,
then use containers-storage mount toplayerid to mount it
The help page for containers-storage mount says it accepts a LayerOrContainerNameOrID, suggesting I should be able to use myimagename directly in the mount command. However, this doesn't work, producing an error layer not known while mounting myiamgename (and, curiously, an extra blank line).
Is this a bug? If not, it's a feature request: could this be made possible?
The text was updated successfully, but these errors were encountered:
Right now, if I want to use the
containers-storage
CLI tool to mount an image so I can explore its filesystem (without creating a container), I seem to have to:containers-storage image myimagename
containers-storage mount toplayerid
to mount itThe help page for
containers-storage mount
says it accepts aLayerOrContainerNameOrID
, suggesting I should be able to usemyimagename
directly in themount
command. However, this doesn't work, producing an errorlayer not known while mounting myiamgename
(and, curiously, an extra blank line).Is this a bug? If not, it's a feature request: could this be made possible?
The text was updated successfully, but these errors were encountered: