Skip to content

Named container workaround fails when container copies data into it #52

@oxisto

Description

@oxisto

This project currently sets up an empty directory as a workaround for a named container but that actually fails when the container tries to copy files into this directory. This can be seen when running a Wordpress container with a named volume.

docker-compose.yml

version: '3.8'
        
services:
  wordpress:
    image: wordpress:latest
    environment:
      WORDPRESS_DB_HOST: db
      WORDPRESS_DB_USER: wordpress
      WORDPRESS_DB_PASSWORD: wordpress
      WORDPRESS_DB_NAME: wordpress
    volumes:
      - wordpress_data:/var/www/html

this results in

wordpress: Error: internalError: "failed to change directory to '/var/www/html' Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory""

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions