第一次尝试 docker 撰写，状态是"restarting"我做错了什么？

Question

这是我第一次尝试使用docker composer(从昨天开始使用docker)，但是docker处于重启状态。

应用程序是Grafana，我通常运行:

docker volume create grafana-storage
docker run -d -p 3000:3000 --name=grafana -v grafana-storage:/var/lib/grafana grafana/grafana

今天我想尝试使用docker composer，以下是我所做的:为docker App创建一个文件夹

sudo mkdir Docker_Applications
cd Docker_Applications
sudo mkdir Grafana

进入目录

cd Grafana
sudo nano docker-compose.yml

添加

version: '3'
services:
grafana:
image: "grafana/grafana:7.3.7"
volumes:
# Data persistency
# sudo mkdir -p /Docker_Applications/Grafana
- "./database:/var/lib/grafana"
- "./config:/etc/grafana"
ports:
- 3000:3000
restart: always

然后运行

root@grafana-dev:/Docker_Applications/Grafana$ sudo docker-compose up -d
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Starting grafana_grafana_1 ... done

状态

root@grafana-dev:/Docker_Applications/Grafana$ sudo docker ps
CONTAINER ID   IMAGE                   COMMAND     CREATED          STATUS                         PORTS     NAMES
a347b12ae9a3   grafana/grafana:7.3.7   "/run.sh"   18 minutes ago   Restarting (1) 4 seconds ago             grafana_grafana_1

希望你能看到我已经尽力了。我想知道这是否与书籍有关。

任何帮助都将非常感激。

我删除了yaml文件的volumes部分，现在它可以运行了。它看起来像权限或者它找不到我的文件夹，我不确定要尝试什么权限/命令。

grafana-dev:/Docker_Applications/Grafana$ sudo docker-compose up
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Creating grafana_grafana_1 ... done
Attaching to grafana_grafana_1
grafana_1  | mkdir: can't create directory '/var/lib/grafana/plugins': Permission denied
grafana_1  | GF_PATHS_CONFIG='/etc/grafana/grafana.ini' is not readable.
grafana_1  | GF_PATHS_DATA='/var/lib/grafana' is not writable.
grafana_1  | You may have issues with file permissions, more information here: http://docs.grafana.org/installation/docker/#migration-from-a-previous-version-of-the-docker-container-to-5-1-or-later

Answer 1

很可能容器在启动过程中由于错误而退出，并且由于您在docker-compose文件中设置了restart: always，容器会自动重新启动。

检查日志或通过删除-d标志来运行docker-compose up非分离，找出问题所在，修复该问题，您的容器将停止不断重新启动自己。