I'm using Colima as a container runtime because I've noticed it is more performant and I barely use the docker desktop UI and obviously that means I'm using sail.
I had to disable the use_screen and use sail binary from vendor just to be able to start the command.
'commands' => [
'About' => 'vendor/bin/sail artisan solo:about',
'Logs' => EnhancedTailCommand::file(storage_path('logs/laravel.log')),
'Make' => new MakeCommand,
'Reverb' => Command::from('vendor/bin/sail artisan reverb:start --debug')->lazy(),
'Pint' => Command::from('vendor/bin/pint --ansi')->lazy(),
],
'use_screen' => (bool) env('SOLO_USE_SCREEN', false),
For some reason it thinks docker is not started even though I have Colima running and everything works when i use CLI

Would appreciate any insights on this.
Thanks for the tool, it must be amazing 😅
I'm using Colima as a container runtime because I've noticed it is more performant and I barely use the docker desktop UI and obviously that means I'm using sail.
I had to disable the
use_screenand usesailbinary from vendor just to be able to start the command.For some reason it thinks docker is not started even though I have Colima running and everything works when i use CLI

Would appreciate any insights on this.
Thanks for the tool, it must be amazing 😅