Allows users to bind mount volumes and directories to litterboxes

[thund-x]

This allows users to share dotfiles between litterboxes. Of course, it can be used to gain malware persistence and access to other litterboxes, so users must be mindful of what they mount. This risk can be mitigated by mounting the volume or directory as read only and/or using the noexec option to prevent binaries from running, though bash totally-innocent-file.sh can still be used, however it's more difficult to type than say ./totally-innocent-file.sh.

[Gerharddc]

Indeed it could be useful to support custom mounts in some way, perhaps only through the .ron definition file since it could be difficult to prompt for on the CLI.

[thund-x]

For #67 there could be a repeating --volume/-v option which is directly passed to podman. As of the interactive way, the program could repeatedly ask the user whether they want to mount a new volume and then ask them for that volume. Something like:

> ...
> Do you want to bind a directory or Podman volume? yes
> Enter value: X:Y:Z
> Do you want to bind a directory or Podman volume? yes
> Enter value: X:Y
> Do you want to bind a directory or Podman volume? yes
> Enter value: X
> Invalid value. Bind mounts follow the following format: SOURCE-VOLUME|HOST-DIR:CONTAINER-DIR[:OPTIONS]
> Do you want to bind a directory or Podman volume? no
> ...

[Gerharddc]

For #67 there could be a repeating --volume/-v option which is directly passed to podman. As of the interactive way, the program could repeatedly ask the user whether they want to mount a new volume and then ask them for that volume.

Fair enough, that does make sense

[Gerharddc]

To some extent this is now supported by #75 which addresses #74 but that doesn't mean it wouldn't be nice to also have something more specific