sure, the default location is /etc/httpd.conf but busybox supports serving the conf file from subdirectories as a feature:

 * If a sub directory contains config file, it is parsed and merged with
 * any existing settings as if it was appended to the original configuration.
 *
 * subdir paths are relative to the containing subdir and thus cannot
 * affect the parent rules.

moving to /etc/httpd.conf would be a breaking change for anyone that doesn't have a blank httpd.conf and relies on their conf being in the project directory.

if you really care about this, the /etc directory is present on the scratch image so you can rewrite the CMD line yourself and still benefit from the pre-built image:

FROM lipanski/docker-static-website:2.4.0

COPY httpd.conf /etc/httpd.conf
COPY index.html .

CMD ["/busybox-httpd", "-f", "-v", "-p", "3000"]

if you want to use COPY . . you should be careful not to include httpd.conf in the mix. you'll want to separate files in subdirectories / have your Dockerfile in a parent directory (or use COPY --exclude if you're running latest buildkit).

this being said, I think the one change I can make here is to reduce the default CMD line from:

CMD ["/busybox-httpd", "-f", "-v", "-p", "3000", "-c", "httpd.conf"]

to:

CMD ["/busybox-httpd", "-f", "-v", "-p", "3000"]

...since this will check both the /etc and the project root. note that the image ships with an empty httpd.conf (see the reason for that here) but this shouldn't conflict with the one under /etc.

at that point you won't even need to overwrite the CMD:

FROM lipanski/docker-static-website:2.5.0

COPY httpd.conf /etc/httpd.conf
COPY index.html .

Uh oh!

put httpd.conf outside of documentroot #36

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions