Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

275
Views
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?

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

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.

over 4 years ago · Santiago Trujillo Report

0

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).

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!