overleaf / overleaf/toolkit

Container mongo Started - Error response from daemon: Container

Open
#322 3 comments 0 reactions 0 assignees View on GitHub

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

When Im installing, in a new ubuntu and clean VM, im always have this error:

  1. bin/up -d
    Initiating Mongo replica set...
    [+] Running 1/1
    ✔ Container mongo Started
    Error response from daemon: Container 07338aa836f6917cfce348fc6f2a72e95020b99a15cc2233492c294c56582296 is restarting, wait until the container is running

Observed Behaviour

bin/start
[+] Running 1/1
✘ Container mongo Error
dependency failed to start: container mongo is unhealthy

Analysis

The result from bin/doctor is:
====== Overleaf Doctor ======

  • Host Information
    • Linux
    • Output of 'lsb_release -a':
      Distributor ID: Ubuntu
      Description: Ubuntu 24.04.1 LTS
      Release: 24.04
      Codename: noble
  • Dependencies
    • bash
      • status: present
      • version info: 5.2.21(1)-release
    • docker
      • status: present
      • version info: Docker version 27.4.1, build b9d17ea
    • realpath
      • status: present
      • version info: realpath (GNU coreutils) 9.4
    • perl
      • status: present
      • version info: 5.038002
    • awk
      • status: present
      • version info: GNU Awk 5.2.1, API 3.2, PMA Avon 8-g1, (GNU MPFR 4.2.1, GNU MP 6.3.0)
    • openssl
      • status: present
      • version info: OpenSSL 3.0.13 30 Jan 2024 (Library: OpenSSL 3.0.13 30 Jan 2024)
    • docker compose
      • status: present
      • version info: Docker Compose version v2.32.1
  • Docker Daemon
    • status: up
    • server version: 27.4.1
      ====== Configuration ======
  • config/version
    • status: present
    • version: 5.2.1
  • config/overleaf.rc
    • status: present
    • values
      • OVERLEAF_DATA_PATH: data/overleaf
      • OVERLEAF_LOG_PATH: not set, keeping logs in container
      • SERVER_PRO: false
      • SIBLING_CONTAINERS_ENABLED: false
      • OVERLEAF_LISTEN_IP: 127.0.0.1
      • OVERLEAF_PORT: 80
      • MONGO_ENABLED: true
      • MONGO_IMAGE: mongo
      • MONGO_VERSION: 6.0
      • MONGO_DATA_PATH: data/mongo
      • REDIS_ENABLED: true
      • REDIS_IMAGE: redis:6.2
      • REDIS_AOF_PERSISTENCE: true
      • REDIS_DATA_PATH: data/redis
      • NGINX_ENABLED: true
      • NGINX_CONFIG_PATH: config/nginx/nginx.conf
      • TLS_PRIVATE_KEY_PATH: config/nginx/certs/overleaf_key.pem
      • TLS_CERTIFICATE_PATH: config/nginx/certs/overleaf_certificate.pem
      • NGINX_HTTP_LISTEN_IP: X.X.X.X
      • NGINX_HTTP_PORT: 80
      • NGINX_TLS_LISTEN_IP: X.X.X.X
      • TLS_PORT: 443
      • GIT_BRIDGE_ENABLED: false
  • config/variables.env
    • status: present
    • values
      • SHARELATEX_FILESTORE_BACKEND: fs
      • SHARELATEX_HISTORY_BACKEND: fs
      • OVERLEAF_FILESTORE_BACKEND: fs
      • OVERLEAF_HISTORY_BACKEND: fs
        ====== Warnings ======
        ! Detected SIBLING_CONTAINERS_ENABLED=false. When not using Sibling containers, users have full read and write access to the 'sharelatex' container resources (filesystem, network, environment variables) when running LaTeX compiles. Only use this mode in environments where all users are trusted and no isolation of users is required.
        ====== End ======

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with bin/up and bin/start, then inspect the Mongo settings referenced by config/overleaf.rc, including MONGO_IMAGE, MONGO_VERSION, and MONGO_DATA_PATH, while reproducing the failure on Ubuntu 24.04 with the listed Docker versions. Done means the Mongo container remains healthy and bin/start completes without the dependency failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, mongodb, shell
Domain
databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.