You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're right, www-data already exists in all the official php images. I'd go a step further and change the user id of www-data to 1000 like this image does (so file permissions are correctly mapped when using the image locally).
As for /app vs /var/www, I think /app is a container convention. Before containers, application files usually were just copied to a permanently running server, in other words they were 'variable' and therefore put into the var folder. Containers are usually deployed as a whole and the application files aren't changed afterwards.
I found the -D issue in the docs and made a PR to fix it here: #1243
I think that's helpful regardless of the existing www-data account, because people might want to use other named accounts. Maybe the example name in the docs should be changed though.
What happened?
I'm currently working through https://frankenphp.dev/docs/docker/#running-with-no-capabilities and see the line
useradd -D ${USER};
mentioned several times.Following through the example:
just prints the commands help.
-D
foruseradd
isprint or change default useradd configuration
.-D
foradduser
isDon't assign a password
From my understanding the intention is to add a user
www-data
without a password on debian? That would beuseradd
without specifying-p
. But even thencat /etc/passwd | grep www-data
show the user already exists, so can it be omitted because it serves nothing?
Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
The one installed in the docker image dunglas/frankenphp
Relevant log output
No response
The text was updated successfully, but these errors were encountered: