overleaf / overleaf/toolkit

mongo command line is not generated correctly when using Podman as backend

Open Beginner friendly
#422 0 comments 1 reaction 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

Description

When running Overleaf with Podman (v5.6.0) as the backend and using the following docker-compose.mongo.yml configuration:

---
services:

    mongo:
        restart: always
        image: "${MONGO_DOCKER_IMAGE}"
        command: "${MONGO_ARGS}"
        container_name: mongo
        volumes:
            - "${MONGO_DATA_PATH}:/data/db"
        expose:
            - 27017
        healthcheck:
            test: echo 'db.stats().ok' | ${MONGOSH} localhost:27017/test --quiet
            interval: 10s
            timeout: 10s
            retries: 5

    sharelatex:
      depends_on:
        mongo:
          condition: service_healthy
      links:
        - mongo

with Podman, it tries to execute --replSet overleaf directly, resulting in the error:
executable file not found in $PATH: No such file or directory: "--replSet"

Steps to reproduce
Just run the toolkit with podman as the provider of the container service.

Expected behavior
Podman should append the command to the image's ENTRYPOINT, just like Docker does, so that "mongod --replSet overleaf" is executed.

Actual behavior
Podman tries to execute --replSet overleaf directly, which fails.

Environment
Client: Podman Engine
Version: 5.6.0
API Version: 5.6.0
Go Version: go1.25.3 (Red Hat 1.25.3-1.el10_1)
Git Commit: b194cd996eb74ecf0ff67d710d4b2aaa90e1c27e
Built: Mon Jan 12 08:00:00 2026
Build Origin: Rocky Linux Build System releng@rockylinux.org
OS/Arch: linux/amd64

Additional context

  • This works as expected in Docker
  • This can be solved by manually setting the command in "lib/docker-compose.mongo.yml" as "mongod --replSet overleaf".

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 lib/docker-compose.mongo.yml and inspect how the Mongo command is defined for the container. Run the toolkit with Podman to reproduce the command-generation failure, then verify that the generated command invokes mongod with --replSet overleaf rather than treating --replSet as the executable.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, infrastructure
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.