Overleaf startup failed after deleting some containers
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Steps to Reproduce
- have successfully strted up overleaf, and stopped
- deleted some containers because of full disk storage, according to https://stackoverflow.com/questions/31712266/how-to-clean-up-docker-overlay-directory, using command
sudo docker system prune -a -f - executing bin/up
Expected Behaviour
a successful startup
Observed Behaviour
~# overleaf/bin/up -d
Initiating Mongo replica set...
WARN[0000] /root/overleaf/config/docker-compose.override.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 1/0
✔ Container mongo Running 0.0s
WARN[0000] /root/overleaf/config/docker-compose.override.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 1/1
✘ sharelatex Error manifest for sharelatex/sharelatex:with-texlive-full not found: manifest ... 31.0s
Error response from daemon: manifest for sharelatex/sharelatex:with-texlive-full not found: manifest unknown: manifest unknown
Context
I was trying to start overleaf, but failed.
Technical Info
bin/start is okay:
~# overleaf/bin/start
WARN[0000] /root/overleaf/config/docker-compose.override.yml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 1/1
✔ Container mongo Healthy
Analysis
I think I've deleted some important containers that is essential to the startup. There seems to be no way to rebuild overleaf again. How can I complement the missing containers?
I am wondering if my data has been deleted (there are tex files stored in my overleaf server). Can I recover my data so that I can try to build a new overleaf?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with bin/up and compare its container and image configuration with bin/start; inspect config/docker-compose.override.yml and the reported sharelatex/sharelatex:with-texlive-full error. Reproduce the startup after docker system prune -a -f if possible, and verify that bin/up completes successfully while the existing stored data remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100