Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Burdyle's avatar

"sail up" creates new container instead of using correct one

Hello!

I created a new app with docker+windows using the official procedure (https://laravel.com/docs/10.x#getting-started-on-windows) and everything has been working fine for a week so far, but as soon as I reboot my computer, if I try "sail up -d" via WSL, it creates a new container instead of using the one I've been using from the beginning...

If I press the play button on the correct container via docker-desktop, it starts correctly but in WSL, it says "Sail is not running

Am I doing anything wrong? Thanks in advance for your help!

0 likes
2 replies
LaryAI's avatar
LaryAI
AI
Best Answer
Level 58

It seems like the issue is related to the Docker container not being recognized by WSL after a computer reboot. Here are a few steps you can try to resolve the problem:

  1. Check if the Docker container is running: Open Docker Desktop and ensure that the container you want to use is running. If it is not running, start it manually.

  2. Restart WSL: Open your WSL terminal and run the following command to restart the WSL service:

wsl --shutdown
  1. Start the Docker container from WSL: In your WSL terminal, navigate to your Laravel project directory and run the following command to start the container:
sail up -d
  1. Verify the container status: Run the following command to check the status of the container:
sail ps

This command should display the running containers. Make sure the container you want to use is listed.

If the above steps don't resolve the issue, you can try the following:

  1. Remove and recreate the container: Run the following command to stop and remove the existing container:
sail down --volumes

Then, start a new container using the following command:

sail up -d
  1. Update Docker Desktop: Make sure you are using the latest version of Docker Desktop. Check for any available updates and install them if necessary.

If the problem still persists, you can seek further assistance on the Laracasts forum or consult the Docker documentation for Windows-specific troubleshooting.

1 like
ArthurPatriot's avatar

Same... After sail up... I got new path each time...

/mnt/wsl/docker-desktop-bind-mounts/Ubuntu-22.04/bdfb86f0beeeab0b70b8d64e111a18a67768a6df524d768aefe7a995bd3ba509

Please or to participate in this conversation.