A container manager inspired by distrobox.
The version number is fairly meaningless as of now. Tagged revisions are what I consider to be in a working state, but I do not guarantee backwards/forwards compatibility.
Why not?
The releases have binaries for x86_64, statically linked with musl. Just extract it and put it in your PATH. Podman is a required runtime dependency for the host; see distrobox's guide to install it without root.
You can optionally symlink the subcommands (though everything will work fine without doing so).
ln -s dizzybox ~/.local/bin/dizzybox-enter
ln -s dizzybox ~/.local/bin/dizzybox-create
ln -s dizzybox ~/.local/bin/dizzybox-rmCompile dizzybox.c with a C compiler. Static linking is recommended to avoid dependency on libc.
Prints out help information; this is not yet very complete.
Enters a container. If command is unspecified, it defaults to the shell configured in the container. chsh can be used in the container to change the shell.
Creates the container with the specified image.
This can be used to upgrade/reinstall the entrypoint.
Removes the specified container. Currently the same as calling podman rm directly.
Experimental, incomplete command to export a desktop entry. Must use full or relative path.
Run profiles/nix.sh. You can then enter with dizzybox enter nix.
If you try to run programs installed with nix-env directly from enter, you will find they are not on the PATH. To fix this, run your command with sh -lc. #+begin_src sh dizzybox enter nix sh -lc 'exec zsh' #+end_src
Currently there's no export, just use shell aliases.
Distrobox is a much more tested and stable utility.
Dizzybox does not install anything in the container by default, including sudo; instead, the --su option can be used on entry.
Dizzybox has fewer host dependencies, only requiring podman to use, and a C compiler to build.
Distrobox's main command is a wrapper for subcommands' scripts; dizzybox uses a monolithic main program which can be symlinked.