Hi, On Tue, 03-Oct-2017 16:35, Burr Sutter wrote: > But profile “bar” does not exist until start is called
The global '--profile bar' option will implicitly create the profile when used with the config an addon command. If you want to configure a given profile prior to start you will need to use these commands with this option. How in your example do you expect minishift to now to what profile to associate the config changes? How would Minishift know that you want to configure a profile bar? As mentioned on the issue comment, maybe a different behaviour for 'minishift profile set bar' makes sense. Atm you get an error message if the profile does not exist. One cold argue it should create an empty profile. Whether there should be an explicit 'minishift profile create bar' is debatable. Either way, your examples would still be wrong and would need to be preceded with a minishift profile [set|create]. --Hardy > > I think there should be a > Minishift profile create that matches delete > Then all other commands work inside of that profile context. > > > On Tue, Oct 3, 2017 at 9:21 AM Hardy Ferentschik <[email protected]> > wrote: > > > On Tue, 03-Oct-2017 14:28, Burr Sutter wrote: > > > any thoughts how the workaround for addons + profiles? > > > > See the comments on the issue you created. You are using the commands > > wrong. You > > issue 'config set' and 'addon enable' commands against the currently > > active profile, but then > > you start a new profile. If you want to set the config and add-ons prior > > to starting the profile > > you need to do something like: > > > > $ minishift --profile bar addon enable anyuid > > > > resp > > > > $ minishift --profile test config set memory 6144 > > > > --Hardy > > > > _______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
