docker does not create folder in nginx html root - nginx

Question

I am trying to create an nginx docker container (to provide file upload/download).
Under the html root I'm looking to create some additional subfolders (upload and download).
I took the nginx docker image as my base and added some additional lines to create/initialise the subfolders.
FROM nginx
MAINTAINER Carl Wainwright <carl.wainwright#ipaccess.com>
ENV HTML_PATH /var/www/html
COPY nginx.conf /etc/nginx/nginx.conf
RUN mkdir -p $HTML_PATH/upload && mkdir -p $HTML_PATH/download
RUN chmod 755 $HTML_PATH/upload && mkdir chmod 755 $HTML_PATH/download
RUN chown nginx:nginx $HTML_PATH/upload && chown nginx:nginx $HTML_PATH/download
In my docker-compose file I am creating my container as follows:
wbh-device-asset-server:
restart: always
image: wbh-device-asset-server/nginx:test
container_name: wbh-device-asset-server
volumes:
- /www-data:/var/www/html
ports:
- "8081:8081"
networks:
- mynetwork
My nginx configuration has the following server configuration.
server {
error_log /var/log/nginx/error.log debug;
access_log /var/log/nginx/access.log main;
# Running port
listen 8081;
# Proxy requests to get SDP's
location ~ \.sdp {
root /var/www/html;
try_files $uri =404;
limit_except GET { deny all; }
}
# Proxy requests to put APD's.
location ~ \.(apd) {
dav_methods PUT;
limit_except PUT { deny all; }
client_body_temp_path /tmp/files/;
client_body_in_file_only on;
client_body_buffer_size 128K;
client_max_body_size 30M;
}
On my local machine /www-data exists and has write permissions.
Each time I bring the container up the contents of /www-data are empty.
Why is it I cannot create folders under /var/www/html/ ? What is stopping me from doing this.
NOTE: As part of my troubleshooting I created a docker image based on centos and installed nginx from packages and I faced the same issue.

Answer 1

The Dockerfile creates an image, this is the definition used to run containers, not the container itself, and is only run once per image creation. So all the RUN commands happen in there and update your image with the directories you expect.
In your docker-compose.yml, which creates containers, you have a host volume mount. Volumes are performed on the container, not the image build, so this directory is mounted after your Dockerfile's RUN commands have already updated the image. With a host volume, the contents of that directory on the host completely overlay the contents of the image, they aren't deleted, but you won't be able to see them in any container with that volume mount. If you used a named volume, and that named volume happened to be empty, e.g. after you created it for the first time, then Docker includes a feature to copy the contents of the image's directory into the volume before mounting it into your container.
So your 3 options are:
Don't use a volume at all and your files will be visible. Not recommended if you want to preserve this data between containers.
Use a named volume. That can be as easy as changing the volume source from a fully qualified directory, /www-data, to a name, www-data. If you do this, you won't be able to manage the contents of that folder easily from your host, Docker will manage it via it's internal directory structure and you'll want to manage it via containers.
Simply add your desired files to the directory on your host. This is the easiest solution when you're starting out, but be aware that users on the host may not match users in the container, so you may see permission and uid errors that you'll need to fix with chmod or chown commands.