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
I want to use NixOS to manage the colima.yaml config for the default profile. NixOS will build a YAML File in a read-only filesystem and creates a symlink to it in the expected path. This fails because colima requires write permissions:
When I move the symlink and copy the contents to the path, it seems that a template is used to write a new configuration file with the values of whatever was read in on startup. While it is great that this allows poorly formatted files to be legible after startup, I'd like a way to tell colima that this unnecessary. For example, colima start --no-config-template or --read-only-config.
The text was updated successfully, but these errors were encountered:
Description
I want to use NixOS to manage the
colima.yaml
config for the default profile. NixOS will build a YAML File in a read-only filesystem and creates a symlink to it in the expected path. This fails because colima requires write permissions:When I move the symlink and copy the contents to the path, it seems that a template is used to write a new configuration file with the values of whatever was read in on startup. While it is great that this allows poorly formatted files to be legible after startup, I'd like a way to tell colima that this unnecessary. For example,
colima start --no-config-template
or--read-only-config
.The text was updated successfully, but these errors were encountered: