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
At the moment there seems to be no way for a user to easily find out what kind of configuration options Distrobox has available
The web page at https://distrobox.it/#configure-distrobox only offers a very short example file, with what I guess is only a very limited subset of configuration keys available.
At minimun, there should be a reference / link, where all the config keys are defined. Even better if there would be a template config file, with documented keys, and a user can place to his system after editing. And even better if the documentation would be online.
For example, I recently learned that there is a assume_yes key, but that is not documented anywhere.
The text was updated successfully, but these errors were encountered:
In this comment, for example, assume_yes is referenced, which could be set to avoid unwanted actions.
This is a problem with your distro's configuration not with distrobox
As you already see it does not forcibly do anything if the config to assume_yes is not set
But I cannot seem to set that anywhere, so it seems impossible to configure such thing at all. Nor do I find any reference of any assume_yes key usage in Distrobox scripts:
There's a possibility for a rather clumsy workaround, but this requires meddling with the backend system command, so it's not working on Distrobox level:
if podman container exists "${containername}"; then
distrobox enter "${containername}"
fi
At the moment there seems to be no way for a user to easily find out what kind of configuration options Distrobox has available
The web page at https://distrobox.it/#configure-distrobox only offers a very short example file, with what I guess is only a very limited subset of configuration keys available.
At minimun, there should be a reference / link, where all the config keys are defined. Even better if there would be a template config file, with documented keys, and a user can place to his system after editing. And even better if the documentation would be online.
For example, I recently learned that there is a
assume_yes
key, but that is not documented anywhere.The text was updated successfully, but these errors were encountered: