containers...mport-layer(1)

containers-storage-import-layer πŸ’–

okay bestie, welcome to the General Commands Manual section for containers-storage-import-layer β€” yes that's the whole name, she's long but she's worth it ✨


✨ NAME ✨

containers-storage-import-layer β€” Import files to a new layer πŸŽ€


🌸 SYNOPSIS 🌸

containers-storage import-layer [options [...]] [parentLayerNameOrID]

πŸ’… DESCRIPTION πŸ’…

so this subcommand is literally a two-for-one combo deal β€” it's containers-storage create-layer and containers-storage apply-diff holding hands 🫢

here's the lore: when a layer first gets created with containers-storage create-layer, it has no changes relative to its parent layer. like, zero, none, a blank slate, main character with no backstory. from there you've got two paths, bestie:

  • mount it read-write and mess with the contents directly, or
  • add stuff (or remove stuff) by applying a layer diff with containers-storage apply-diff.

that's it, that's the vibe check. πŸ’œ


πŸ‘‘ OPTIONS πŸ‘‘

  • -n name β€” sets an optional name for the layer. but heads up: if that name is already taken, you get an error. no name-stealing allowed πŸ™ˆ
  • -i | --id ID β€” sets the ID for the layer. if you don't specify one, she'll just generate one for you ✨
  • -f | --file filename β€” tells it which file the diff should be read from. if you don't use this option, the diff gets read from standard input instead πŸ“₯
  • -l | --label mount-label β€” sets the label that should be assigned as an SELinux context when the layer gets mounted 🏷️
  • -r | --readonly β€” marks the layer as readonly. she's off the market, no edits πŸ”’
  • -j | --json β€” prefer JSON output 🧾
  • --uidmap β€” a UID map specified in the format expected by subuid. it cannot be specified simultaneously with --hostuidmap 🚫
  • --gidmap β€” a GID map specified in the format expected by subgid. it cannot be specified simultaneously with --hostuidmap 🚫
  • --hostuidmap β€” force host UID map. it cannot be specified simultaneously with --uidmap or --subuidmap πŸ™…β™€οΈ
  • --hostgidmap β€” force host GID map. it cannot be specified simultaneously with --gidmap or --subgidmap πŸ™…β™€οΈ
  • --subuidmap username β€” create a UID map for username using the data from /etc/subuid. it cannot be specified simultaneously with --hostuidmap 🚫
  • --subgidmap group-name β€” create a GID map for group-name using the data from /etc/subgid. it cannot be specified simultaneously with --hostuidmap 🚫
not me warning you twice but fr fr, those map options are giving "pick a lane" energy β€” mix the wrong ones and it's a no πŸ’€

πŸ¦‹ EXAMPLE πŸ¦‹

containers-storage import-layer -f 71841c97e320d6cde.tar.gz -n new-layer somelayer

ate, no crumbs. πŸ”₯


🌈 SEE ALSO 🌈

go read those next bestie, they're iconic too πŸ’–


and that's the whole page, periodt πŸ’… this little writeup is from the General Commands Manual source, version dated April 2019, filed under containers...mport-layer(1) β€” mwah, take care of her πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from