PS C:\DEV\Docker\bee> cmd
Microsoft Windows [Version 10.0.22000.739]
(c) Microsoft Corporation. All rights reserved.
C:\DEV\Docker\bee>bash ./vendor/bin/sail up -d
[+] Building 0.0s (0/0)
[+] Running 2/2
✔ Network d4cd61d598f66cbacae9e0f2011834f55d902bceffd4f47ec74d3aaecc3351a3_bridge Created 0.0s
✔ Container d4cd61d598f66cbacae9e0f2011834f55d902bceffd4f47ec74d3aaecc3351a3-laravel.test-1 Started 0.4s
C:\DEV\Docker\bee>bash ./vendor/bin/sail artisan config:cache
Sail is not running.
You may Sail using the following commands: './vendor/bin/sail up' or './vendor/bin/sail up -d'
I have this strange issue where container builds and runs just fine: both attached/detached and http://localhost is working, but I'm getting
Sail is not running. and sail ps returns no containers
C:\DEV\Docker\bee>bash ./vendor/laravel/sail/bin/sail ps
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
but docker ps works just fine
C:\DEV\Docker\bee>docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
430ee416a732 sail-8.1/app "start-container" 4 minutes ago Up 4 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:5173->5173/tcp, 8000/tcp d4cd61d598f66cbacae9e0f2011834f55d902bceffd4f47ec74d3aaecc3351a3-laravel.test-1
I'm running Windows 11 with WSL Ubuntu as default. Any ideas would be appreciated.