You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently toolbox will default to your home directory. Because of this I cannot use toolbox for other purposes (isolated, work projects etc). I love the automatic integration with X as well as automatically mounting /dev for me however I believe having option to specify custom $HOME path for container would be a very useful feature.
I would like to be able to specify custom $HOME path for each toolbox container on the host so that there is no conflicting config files for cloud environments such as Azure or AWS, python modules etc. Ideally if we would have something like .toolboxrc file in which we could define custom configurations for tagged containers and allow tagging when using toolbox create command?.
I am aware that I could create podman containers with CMDlines from toolbox however I believe it would be more convenient to have this functionality within toolbox itself.
The text was updated successfully, but these errors were encountered:
Currently toolbox will default to your home directory. Because of this I cannot use toolbox for other purposes (isolated, work projects etc). I love the automatic integration with X as well as automatically mounting
/dev
for me however I believe having option to specify custom $HOME path for container would be a very useful feature.I would like to be able to specify custom $HOME path for each toolbox container on the host so that there is no conflicting config files for cloud environments such as Azure or AWS, python modules etc. Ideally if we would have something like .toolboxrc file in which we could define custom configurations for tagged containers and allow tagging when using
toolbox create command
?.I am aware that I could create podman containers with CMDlines from toolbox however I believe it would be more convenient to have this functionality within toolbox itself.
The text was updated successfully, but these errors were encountered: