Sail is not working when using docker-desktop for Linux

[jurios]

• Sail Version: 1.20.1
• Laravel Version: 9.51.0
• PHP Version: Using sail with 8.2
• Host operating system: Linux Ubuntu 22.04.1

Description:

This bug is reproducible in Linux. Not sure what happens on MacOS or Windows.

When I run sail using the docker engine, the files in the container are assigned to sail/sail .
The user/group is the expected one thus laravel.test webserver is able to serve the files with no problem.

However, when run sail using the desktop-linux context (which is the context used by docker-desktop), owner/group are not correctly set to sail/sail.
Looks like volumes are handled a bit different when using docker-desktop: https://docs.docker.com/desktop/faqs/linuxfaqs/#how-do-i-enable-file-sharing

As the owner/group have changed, the webserver is not able to serve the website:

The stream or file "/var/www/html/storage/logs/laravel.log" could not be opened in append mode: Failed to open stream: Permission denied

Steps To Reproduce:

1. Install docker engine and docker-desktop in a Linux system and run both.
2. Switch the context to use docker engine running the following command: docker context use default
3. Run sail and check owner/group of the shared files in the container:

sail up -d
docker exec -it example-app-laravel.test-1 ls -l

You should see something like this:

drwxr-xr-x  7 sail sail   4096 Jan 31 15:05 app
-rwxr-xr-x  1 sail sail   1686 Jan 31 15:05 artisan
...

4. Stop sail: sail down
5. Change the context in order to use docker-desktop with docker context use desktop-linux
6. And run the same commands

sail up -d
docker exec -it example-app-laravel.test-1 ls -l

That's the output:

drwxr-xr-x  7 root root   4096 Jan 31 15:05 app
-rwxr-xr-x  1 root root   1686 Jan 31 15:05 artisan
...

As you can see file's owner/group changed.

Solutions

Not sure. At the moment looks like avoid using docker desktop in Linux and use docker engine instead is a workaround.

Related: #459

[github-actions]

Thank you for reporting this issue!

As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.

If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.

Thank you!

[taylorotwell]

Thanks for the report - if you're able to come across a fix please submit a PR. 👍

[jurios]

I'm not a docker expert but..yeah I give it a try!

[OceManiac]

Facing the same Issue. Like mentioned in the Docker FAQ, i tried to set up a recursive ACL for the Laravel dir. But this does not work for newly created files with sail artisan make commands.

Best Workaround i found so far is using the sail root-shell only.

You should start by login into the root shell and execute the following commands for initial set-up:

php artisan storage:link 
php artisan optimize:clear (otherwise i got permission denied when writing into cache)
php artisan optimize (to recreate cache dir)

All subsequent artisan commands should be fired inside the root shell.
All files inside the Docker Container will be owned by root:root. On the host system the files will be mapped to the user with the UID=1000 and GID=1000 (my default user) . This works fine for me.

Hope this helps.

[devjk1]

I am also having the same issue. Project owner is 1000. Project owner in Sail is root causing permission issues when I open localhost.
OS: Fedora 37 also Debian 11

[iron-viper]

Hello, have the same issue, when host's machine files have 1000 id but in the container it's runed as root(id=0). Ubuntu 20.04
And I have the error:

The stream or file "/var/www/html/storage/logs/laravel.log" could not be op  
2023-04-13T11:45:46.088107194Z   ened in append mode: Failed to open stream: Permission denied                
2023-04-13T11:45:46.088109137Z   The exception occurred while attempting to log: Path "/var/www/html/storage  
2023-04-13T11:45:46.088111052Z   /clockwork" is not writable.                                                 
2023-04-13T11:45:46.088121578Z   Context: {"exception":{}}      

[francoism90]

Could you guys give more details? What distro are you using and if you're running Docker rootless?
It seems Docker Desktop (not using it - so cannot test) runs as rootless.

This could help: #536 (comment)

[Zamerick]

Adding some context here so maybe someone more docker savvy can use it to resolve this issue: I'm using the desktop-linux docker context, and if you change php to run under root instead of sail in the supervisord.conf, it will (correctly?) set the permissions of at least the storage folder to 1337:sail, though it will still be wrong since then php is expecting the root user.

[NickSdot]

Seems related to this: docker/desktop-linux#81 (comment)

[nunomaduro]

After looking into this matter, it seems like we can't fix it on our end because it's a bug in Docker For Linux. But here's the good news: the Docker For Linux team is on it and working closely to get it sorted! You can keep track of the progress and resolution of this issue over here: docker/desktop-linux#81.

[francoism90]

@nunomaduro You have seen this is from 2022 right?

It is a configuration issue at your end, as you create a user with a different ID. If they match, like I said before, it will work fine.

[jurios]

Hi there,

sorry but I wasn't able to tackle this. I had to be (and I'm still) afk because a disease.

Thanks @nunomaduro and all of you for taking a look :)

By the way, If there is not a fix, what about leave a note in the sail documentation?

[Gaudenz77]

To all who feel a bit lost after weeks of messing around with chmod and chown, sail:sail, composer problems or whatnot: As long as docker Desktop permission issues arent fixed and work like everywhere else (docker Desktop Windows and Mac, using only docker engine (docker ce) in linux): DO NOT USE DOCKER DESKTOP FOR LINUX. IT WONT WORK OUT OF THE BOX YET. A docker devteam: Please try to fix this. After first being positively impressed by docker desktop features rich app, I had to remove it completely and work now without ANY ISSUES using docker engine and docker compose.