KRAFT-CLOUD-VOLUME-IMPORT(1)

πŸ“¦ version 0.12.16, in nixos 26.05, nixpkgs unstable

πŸ’Ύ kraft-cloud-volume-import β€” bestie edition ✨

okay so real talk: this is the KraftKit CLI page for kraft-cloud-volume-import, and it's literally the glow-up your persistent volume has been waiting for πŸ’…


🌸 NAME 🌸

kraft-cloud-volume-import β€” import local data to a persistent volume πŸŽ€


✨ SYNOPSIS ✨

kraft cloud volume import [FLAGS]

yeah that's it, that's the whole vibe β€” you run it with flags, that's the assignment 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

Import local data to a persistent volume. that's the whole thing, no cap β€” you've got data sitting on your machine, you want it on a volume in the cloud, this is the command that makes it happen ✨


πŸ’… OPTIONS πŸ’…

  • -f, --force[=false] β€” force the import, even if it might fail πŸ™ˆ (yes, it says that. it knows. it's giving reckless but iconic)
  • -h, --help[=false] β€” help for import, aka the "wait what does this do again" button
  • --image="official/utils/volimport:1.0" β€” the volume import image to use πŸ‘‘ default is official/utils/volimport:1.0 and honestly she's the main character
  • -p, --port=42069 β€” custom port to connect to the volume import service instance on πŸ”₯ default sits at 42069 which. yeah. they knew.
  • -s, --source="." β€” path to the data source (directory, Dockerfile, Docker link, cpio file) πŸ“ defaults to . so it just grabs what's right there
  • -t, --timeout=10 β€” timeout for the import process in seconds when unresponsive ⏳ so like, 10 whole seconds is the default patience level
  • -v, --volume="" β€” identifier of an existing volume (name or UUID) πŸ’– empty by default, so you gotta tell it which one
  • -w, --workdir="" β€” working directory for the import process 🌈 also empty by default

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these bad boys come from the parent command, so they're yours for free, iykyk:

  • --allow-insecure[=false] β€” allow insecure connections to the Unikraft Cloud API 😭 (default is false, keep it that way unless you know what you're doing fr fr)
  • --metro="" β€” Unikraft Cloud metro location 🌍
  • --token="" β€” Unikraft Cloud access token πŸ”‘ (yes it's empty by default, go put your token in)

⭐ EXAMPLES ⭐

okay bestie, here's the part where it gets fun β€” every single one of these is a real, working invocation:

# Import data from a local directory "path/to/data" to a volume named "my-volume"
$ kraft cloud volume import --source path/to/data --volume my-volume
# Import data from a local Dockerfile "path/to/Dockerfile" to a volume named "my-volume"
$ kraft cloud volume import --source path/to/Dockerfile --volume my-volume
# Import data from a docker registry "docker.io/nginx:latest" to a volume named "my-volume"
$ kraft cloud volume import --source docker.io/nginx:latest --volume my-volume
# Import data from a local cpio file "path/to/file" to a volume named "my-volume"
$ kraft cloud volume import --source path/to/file --volume my-volume
# Import data from a local cpio file "path/to/file" to a volume named "my-volume" on the port 10000
$ kraft cloud volume import --source path/to/file --volume my-volume --port 10000

see how the last one swaps the port to 10000? that's the little flex at the end πŸ’…


πŸ‘€ SEE ALSO πŸ‘€


πŸ“œ HISTORY πŸ“œ

1-Jan-1980 β€” auto generated by KraftKit. iconic date, truly the blueprint πŸŽ€


ngl, if you're importing real data, double-check your --volume value before you go β€” an empty default means it needs you to be specific πŸ’–

so yeah, that's the whole page, and it was documented by KraftKit (that's the source, and the version vibe is KraftKit CLI), dated Jan 1980 in the original footer πŸ“… β€” consider this your cute lil sign-off, bestie. go import something slay βœ¨πŸ’…πŸ¦‹

πŸ“¦ where this page comes from