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
If you configure your config with kubernetes configuration it will not automatically populate cluster-setting file on Debian.
~/.config/kurtosis/kurtosis-config.yml
It will fail with:
Error: An error occurred running command 'start'
Caused by: An error occurred creating an engine manager
Caused by: An error occurred getting the Kurtosis cluster config
Caused by: Expected to find Kurtosis configuration for cluster '', instead found nothing
To fix the issue, you can manually create cluster-setting at ~/.local/share/kurtosis/cluster-setting and set it to docker with no new linebreak.
echo -n "docker" > ~/.local/share/kurtosis/cluster-setting then do a kurtosis engine restart
Desired behavior
Ideally when someone installs kurtosis for the first time it should create the cluster-setting file as well, and populate it with docker. It would be very nice to have this file also located in the same directory as kurtosis config, instead of a completely other seemingly random dir.
It is already in the same dir on macos.
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered:
What's your CLI version?
1.4.1
Description & steps to reproduce
If you configure your config with kubernetes configuration it will not automatically populate cluster-setting file on Debian.
~/.config/kurtosis/kurtosis-config.yml
It will fail with:
To fix the issue, you can manually create cluster-setting at
~/.local/share/kurtosis/cluster-setting
and set it todocker
with no new linebreak.echo -n "docker" > ~/.local/share/kurtosis/cluster-setting
then do akurtosis engine restart
Desired behavior
Ideally when someone installs kurtosis for the first time it should create the cluster-setting file as well, and populate it with docker. It would be very nice to have this file also located in the same directory as kurtosis config, instead of a completely other seemingly random dir.
It is already in the same dir on macos.
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered: