search

NVIDIA / enroot

A simple yet powerful tool to turn traditional container/OS images into unprivileged sandboxes.
Apache License 2.0
648 stars 94 forks source link

Multiple ENROOT_DATA_PATH #66

Open krono opened 3 years ago

krono commented 3 years ago

Currently, ENROOT_DATA_PATH is a single directory (in XDG_DATA_HOME by default) where the containers "live".

A PATH-like behaviour for looking up containers would be neat. So we can have user-specific, machine-specific, and global, potentially reusable containers. But that's just a rough idea

martialblog commented 3 years ago

I've been thinking about this. Been wondering how this might work from the users perspective, by that I mean: would I be able to control where my container will live? If so how?

Currently, the variable is used like this rootfs=$(common::realpath "${ENROOT_DATA_PATH}/${rootfs}") to determine the path...

I don't know if it's practical to add another option to enroot create, e.g. --path. That would probably add quite some logic to the create() function.

krono commented 2 years ago

That's true; any change here is going to increase complexity quite a bit…