CODEWITHSUNDEEP
dockergitlabqnapgitea
mignz
mignz

Reputation: 3918

Docker containers won't start again after being stopped

I'm trying to launch a GitLab or Gitea docker container in my QNAP NAS (Container Station) and, for some reason, when I restart the container, it won't start back up because files are lost (it seems).

For example, for GitLab it gives me errors saying runsvdir-start and gitlab-ctl don't exist. For Gitea it's the s6-supervise file.

Now I am launching the container like this, just to keep it simple:

docker run -d --privileged --restart always gitea/gitea:latest

A simple docker stop .... and docker start .... breaks it. How do I troubleshoot something like this?

Upvotes: 2

Views: 1405

Answers (2)

mignz
mignz

Reputation: 3918

QNAP has sent this issue to R&D and they were able to replicate it. It's a bug and will probably be fixed in a new Container Station update.

It's now fixed in QTS 4.3.6.20190906 and later.

Upvotes: 2

seddikomar
seddikomar

Reputation: 825

Normal to lose you data if you launch just : 

docker run -d --privileged --restart always gitea/gitea:latest

You should use VOLUME to sharing folder between your host and docker host for example :

docker run -d --privileged -v ./gitea:/data -p 3000:3000 -p 222:22 --restart always gitea/gitea:latest

Or use docker-compose.yml (see the official docs).

Upvotes: 0

Related Questions