码头工人卷创建-设置权限

Question

I'm running this on debian 9

I'm using sudo docker volume create db to create a volume I'm using in my docker-compose.yml . But I still get the error db_1_d89b59353579 | mkdir: cannot create directory '/var/lib/mysql': Permission denied db_1_d89b59353579 | mkdir: cannot create directory '/var/lib/mysql': Permission denied .

How can I set permissions for the user using that volume. And how to get the user?

Docker-Compose:

version: '2'

volumes:
  nextcloud:
  db:

services:
  db:
    image: mariadb
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    restart: always
    volumes:
      - db:/var/lib/mysql:z
    environment:
      - MYSQL_ROOT_PASSWORD=***
      - MYSQL_PASSWORD=***
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  app:
    image: nextcloud
    ports:
      - 8080:80
    links:
      - db
    volumes:
      - nextcloud:/var/www/html
    restart: always

I got an install.sh file where I run:

...
sudo docker volume create db

sudo docker-compose build
docker-compose up -d

Answer 1

Try to first change the mounts to local folders and see if that fixes your issue:

version: '2'

volumes:
  nextcloud:
  db:

services:
  db:
...
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=***
      - MYSQL_PASSWORD=***
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  app:
...
    volumes:
      - ./nextcloud:/var/www/html
    restart: always

If that does then check that the volumes are correctly removed by docker-compose down . Run docker volume ls . If they still persist then remove them by hand and rerun your containers with the volumes.

Regarding the difference between mounting to a volume (db:/var/lib/mysql) and mounting to a host path (./db:/var/lib/mysql) :

In the first case it is a volume managed by Docker . It is meant for persistence but getting to the files is a bit more tricky. In the second case it is a path on the host and it makes it a lot easier to retrieve persisted files. I recommend to run "docker-compose config" for both situations and see the difference in how docker-compose internally transforms the statement.