I've no idea why use 82 as uid for www-data

[mcwz]

laradock/nginx/Dockerfile

Line 25 in 123e52e

adduser -u 82 -D -S -G www-data www-data && exit 0 ; exit 1

But in nginx container , /var/www is belong to uid 1000.
When I open app.test ,it shows 404 .

[waiyan13]

This. I was racking my brain for hours why my source folder is owned by 1000.

I wanted to use separate app.conf instead of default.conf inside nginx/sites/. If I used this way, I can't access the index.html I put inside the source folder. Putting it inside public folder didn't help either.

The only way this works is to use default.conf and add your source folder explicitly. I want to know the reason why I can't use custom site configuration.

[ernst77]

I am having alot of issues with UID's and permissions... For example log file get's set by different user each time some containers run as a root some of them as laradock user... And not all of the containers can write logs.

[kenng]

@mcwz @ErnestStaug

spent some time to check on this, for Nginx with php-fpm, it's the php-fpm container that responsible for creating the file in the mounted volume, thus inherited the www-data user id and gid of it.

Therefore you should check in php-fpm container the user www-data and make sure it has access to the mounted volume or permission denied will happen. For our case, new file created initially was set with 1000:33, which resulted no permission to write (since allowed group id is 82 on mounted volume)

try to add the group 82 to the www-data user in php-fpm container.

[stale]

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

[stale]

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.