-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chown www-data
but httpd runs as user daemon
#10
Comments
Oh hmm, this is an interesting one. I'm not sure how we missed it (sorry!) but I think I'm actually leaning towards swapping |
I'd like to re-emphasize the opposite preference :-P. The name of the user varies between distributions, so there isn't one standard we could suggest changing upstream to use. That said, upstream probably should use I believe using a well-known name would avoid some confusion. Everyone hits permission errors at some point :). There's a lot of instructions out there that talk about I suspect upstream specifies |
Is there an update on this one? I would love to see a comprehensible user selection. |
Any update on this? I kept looking quite a long time, because I was creating a mod_cache_disk directory, and I could not get it to write successfully. |
A possible work-around for this issue is to mount an alternate httpd configuration that sets the
In my testing this works as the www-user is specified in While this is not an elegant solution, it helps to understand alternate options. |
I ran into this issue. I kept using |
This is most likely user error: in your apache configuration file (httpd.conf), fix this issue by writing something like the following:
|
The problem happens because the default config file has One easy fix is use this sed to change also |
The default httpd.conf sets
User daemon
. So it's kind of odd to havechown www-data
in the Dockerfile. (www-data is the default when you install the apache packages from debian, as opposed to the upstream tarball).It's not exactly a bug - it works because the directory is readable by any user. However it could cause confusion if you need Apache to have write access somewhere.
Fortunately the PHP+Apache image sets
User www-data
in httpd.conf. MaybeUser www-data
(and Group) should be added to thesed
command in this Dockerfile, which edits the config file?The text was updated successfully, but these errors were encountered: