Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compose structure seems not to work, only starts mongo container #272

Closed
afmart opened this issue Jul 17, 2024 · 7 comments · Fixed by #276
Closed

compose structure seems not to work, only starts mongo container #272

afmart opened this issue Jul 17, 2024 · 7 comments · Fixed by #276

Comments

@afmart
Copy link

afmart commented Jul 17, 2024

Steps to Reproduce

  1. Install docker engine on Alma Linux 9
  2. Clone repository to /opt/overleaf-toolkit
  3. Go into /opt/overleaf-toolkit and run bin/init
  4. Run bin/up
  5. Only "mongo" container is downloaded and created

Expected Behaviour

It should create all needed containers!

Observed Behaviour

image
image

Running the "init" or "start" command only downloads the image and creates the database container "mongo"

Context

Following the quick guide we can't deploy overleaf.

Technical Info

  • URL:
  • Browser Name and version:
  • Operating System and version (desktop or mobile): Alma Linux 9.3
  • Signed in as:
  • Project and/or file:

Analysis

====== Overleaf Doctor ======

  • Host Information
    • Linux
    • lsb_release not found !
  • Dependencies
    • bash
      • status: present
      • version info: 5.1.8(1)-release
    • docker
      • status: present
      • version info: Docker version 27.0.3, build 7d4bcd8
    • realpath
      • status: present
      • version info: realpath (GNU coreutils) 8.32
    • perl
      • status: present
      • version info: 5.032001
    • awk
      • status: present
      • version info: GNU Awk 5.1.0, API: 3.0 (GNU MPFR 4.1.0-p9, GNU MP 6.2.0)
    • openssl
      • status: present
      • version info: OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
    • docker compose
      • status: present
      • version info: Docker Compose version v2.28.1
  • Docker Daemon
    • status: up
    • server version: 27.0.3
      ====== Configuration ======
  • config/version
    • status: present
    • version: 5.1.0
  • config/overleaf.rc
    • status: present
    • values
      • OVERLEAF_DATA_PATH: data/overleaf
      • SERVER_PRO: false
      • OVERLEAF_LISTEN_IP: 127.0.0.1
      • OVERLEAF_PORT: 80
      • MONGO_ENABLED: true
      • MONGO_IMAGE: mongo
      • MONGO_DATA_PATH: data/mongo
      • REDIS_ENABLED: true
      • REDIS_IMAGE: redis:6.2
      • REDIS_AOF_PERSISTENCE: true
      • REDIS_DATA_PATH: data/redis
      • NGINX_ENABLED: false
      • 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: 127.0.1.1
      • NGINX_HTTP_PORT: 80
      • NGINX_TLS_LISTEN_IP: 127.0.1.1
      • 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 ======
  • None, all good
    ====== End ======
@Tunfisch96
Copy link

Hey, I have the same problem. Did a bit of testing and the last commit that is working for me is 2bc0c9d.
I cloned the repository and did a git checkout 2bc0c9d71bb8e1ab94456b89e0dd7cef7810f4bd before the init.

@afmart
Copy link
Author

afmart commented Jul 18, 2024

Ty, I will try to get that version.

@archham
Copy link

archham commented Jul 19, 2024

Same problem here, will try to use this workaround.

Hey, I have the same problem. Did a bit of testing and the last commit that is working for me is 2bc0c9d. I cloned the repository and did a git checkout 2bc0c9d71bb8e1ab94456b89e0dd7cef7810f4bd before the init.

@zhuohaoyu
Copy link

Same problem, looks like they made it impossible for CE to run.

@vidlb
Copy link

vidlb commented Jul 25, 2024

Thanks to @Tunfisch96 comment about last usable commit, I read the diff and found out this is linked to the new env variable SIBLING_CONTAINERS_ENABLED.
The doc here states that it requires SERVER_PRO=true. It looks like SERVER_PRO=false + SIBLING_CONTAINERS_ENABLED=true will prevent docker to pull and run images. Setting SIBLING_CONTAINERS_ENABLED=false in overleaf.rc fixed it for me !

So the issue is simply that the init seed value for this variable should be false, as stated in the docs.

@Karonolandiis
Copy link

Thanks to @Tunfisch96 comment about last usable commit, I read the diff and found out this is linked to the new env variable SIBLING_CONTAINERS_ENABLED. The doc here states that it requires SERVER_PRO=true. It looks like SERVER_PRO=false + SIBLING_CONTAINERS_ENABLED=true will prevent docker to pull and run images. Setting SIBLING_CONTAINERS_ENABLED=false in overleaf.rc fixed it for me !

So the issue is simply that the init seed value for this variable should be false, as stated in the docs.

That so cool! Thank you very much!!!

@das7pad
Copy link
Member

das7pad commented Jul 29, 2024

Thanks for flagging this up. #276 should fix this issue. You can use bin/upgrade to pull in these changes. Sorry for any inconvenience this has caused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants