KRAFT-PKG-PUSH(1)

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

πŸ¦‹ KRAFT-PKG-PUSH(1) πŸ¦‹

okay bestie, welcome to KraftKit CLI β€” this one lives in the KraftKit Manual, and it's literally the glow-up your unikernel package deserves πŸ’…


✨ NAME ✨

kraft-pkg-push β€” push a Unikraft unikernel package to a registry πŸŽ€

🌸 SYNOPSIS 🌸

kraft pkg push [FLAGS] [PACKAGE]

πŸ’– DESCRIPTION πŸ’–

So the vibe here is: you've got a Unikraft unikernel, or a component microlibrary, and you wanna yeet it to a remote location. That's it, that's the whole personality. It pushes. It slays. It sends your stuff to a remote location ✨

πŸ”₯ OPTIONS πŸ”₯

  • -M, --as="auto" β€” force the packaging despite possible conflicts πŸ™ˆ like, yes there might be drama but we're doing it anyway, default is "auto".
  • -h, --help[=false] β€” help for push 🫢 your little "what does this even do" button, defaults to false.
  • -K, --kraftfile="" β€” set an alternative path of the Kraftfile πŸ—‚οΈ if your Kraftfile is not where it's expected, point at it here, default is "".

⭐ EXAMPLES ⭐

push the image for a project in the current directory, easy peasy:

# Push the image for a project in the current directory
$ kraft pkg push

push the image for a project at a path, with tag latest:

# Push the image for a project at a path with tag latest
$ kraft pkg push /path/to/app

push the image with a given name β€” putting the whole name in the group chat:

# Push the image with a given name
$ kraft pkg push unikraft.org/helloworld:latest

πŸ‘‘ SEE ALSO πŸ‘‘

kraft-pkg(1) β€” the rest of the pkg saga, go read it, iykyk πŸ’œ

🌈 HISTORY 🌈

1-Jan-1980 β€” auto generated by KraftKit 🧚 (yeah, the timestamp is giving time-traveler, don't ask, it's iconic)


and that's the whole page, bestie! πŸ’– this beauty is from the KraftKit Documentation, dated Jan 1980, and it's the KraftKit CLI(1) β€” no cap, go push something gorgeous πŸ¦‹βœ¨ πŸŽ€

πŸ“¦ where this page comes from