Can't build angular dist, if nginx is running (dockerized)

Question

The setup

I have 2 docker containers running on Windows 8.1

One containing npm for building an angular project. The other containing nginx, serving the dist directory.

The dist directory is in /var/www/front, shared by both containers in volumes.

Here's the docker-compose config :

nginx:
    build: ./docker/nginx
    ports:
        - "80:80"
        - "8080:8080"
    environment:
        APP_ENV: prod
    volumes:
        - ./logs/nginx:/var/log/nginx:cached
        - ./back:/var/www/back
        - ./front:/var/www/front
node:
    build: ./docker/node
    ports:
        - "4200:4200"
    volumes:
        - ./front:/var/www/front
        - /var/www/front/node_modules/

The issue

When nginx container is running and only when the page is displayed on the browser, ng build won't build the angular project, failing with a "conflict" error :

ETXTBSY: text file is busy, unlink '/var/www/front/dist/assets/image.jpg

Is there a workaround to this issue?

Answer 1

I think the Windows file system locks the files used by the second container, This can result in your error. Using named volumes to share the data between the two containers could solve this problem.

nginx:
    build: ./docker/nginx
    ports:
        - "80:80"
        - "8080:8080"
    environment:
        APP_ENV: prod
    volumes:
        - ./logs/nginx:/var/log/nginx:cached
        - ./back:/var/www/back
        - ./front:/var/www/front
        - dist:/var/www/front/dist
node:
    build: ./docker/node
    ports:
        - "4200:4200"
    volumes:
        - ./front:/var/www/front
        - dist:/var/www/front/dist
        - /var/www/front/node_modules/

volumes:
    dist:

Update :

The issue here was the front/dist output directory which was shared between the 2 containers, but also with the host, running Windows. For some reasons the files were locked on "read-only mode" when the 2 containers read them.

The solution is to create a named volume just for the output directory so that there's no binding with the host path. The 2 containers will read and write files without issues.

The only downside is that the output files will be more difficult to be accessed by the host. Example, for versioning purpose.