-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cannot connect to mongodb #25
Comments
Can you share your compose file? Please note, that docker-compose.yml in this repository is not suited for production use. |
Hi,
Thanks for the fast answer, sorry for the late response. I attached the
file, I did not change anything but the port number on line 14.
KR,
Ch.
Am Mi., 21. Juni 2023 um 13:18 Uhr schrieb Jonas ***@***.***>:
… Can you share your compose file? Please note, that docker-compose.yml
<https://github.com/tuetenk0pp/sharelatex-full/blob/master/docker-compose.yml>
in this repository is not suited for production use.
—
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPRDROCO7PXEYA4DMIXDKLXMLJ73ANCNFSM6AAAAAAZOSRE4I>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
--
(0-0)
---------oOO--(_)--OOo-----------------------------------------------
Christof Bodner ***@***.***>
Linux - Life is too short for reboots
- First they ignore you. Then they laugh at you. Then they
fight you(*). Then you win. -- Ghandi
---------------------------------------------------------------------
email: ***@***.***
QTH: JN66WO
Signal: +43 650 7215383 (http://signal.org)
---------------------------------------------------------------------
GnuPG public key: 0xB15DA60F (http://wwwkeys.eu.pgp.net) Fingerprint 5222
4DEA 773A 60B3 22F9 D244 15EF 6645 B15D A60F
---------------------------------------------------------------------
|
Sorry, GitHub does not show attached files from email. Could you upload the file via the webgui? Also, I noticed that you used |
I tried docker compose up, it'salso failing with Mongodb transaction
numbers.
# This is meant for use in development, use the method described in
README.md for deployment instead.
version: '2.2'
services:
sharelatex:
restart: always
image: tuetenk0pp/sharelatex-full:latest
container_name: sharelatex-full
depends_on:
mongo:
condition: service_healthy
redis:
condition: service_started
ports:
- 8000:80
links:
- mongo
- redis
volumes:
- sharelatex_data:/var/lib/sharelatex
environment:
SHARELATEX_APP_NAME: Overleaf Community Edition
SHARELATEX_MONGO_URL: mongodb://mongo/sharelatex
# Same property, unfortunately with different names in
# different locations
SHARELATEX_REDIS_HOST: redis
REDIS_HOST: redis
ENABLED_LINKED_FILE_TYPES: 'project_file,project_output_file'
# Enables Thumbnail generation using ImageMagick
ENABLE_CONVERSIONS: 'true'
# Disables email confirmation requirement
EMAIL_CONFIRMATION_DISABLED: 'true'
# temporary fix for LuaLaTex compiles
# see overleaf/overleaf#695
TEXMFVAR: /var/lib/sharelatex/tmp/texmf-var
mongo:
restart: always
image: mongo:4.4
container_name: mongo
expose:
- 27017
volumes:
- mongo_data:/data/db
healthcheck:
test: echo 'db.stats().ok' | mongo localhost:27017/test --quiet
interval: 10s
timeout: 10s
retries: 5
redis:
restart: always
image: redis:5
container_name: redis
expose:
- 6379
volumes:
- redis_data:/data
volumes:
sharelatex_data:
mongo_data:
redis_data:
Am Mo., 26. Juni 2023 um 09:25 Uhr schrieb Jonas ***@***.***>:
… Sorry, GitHub does not show attached files from email. Could you upload
the file via the webgui? Also, I noticed that you used docker compose
start instead of the docker compose up command. Maybe that makes a
difference.
—
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPRDROVNVQL7Z3VGMN3VK3XNE2OFANCNFSM6AAAAAAZOSRE4I>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
--
(0-0)
---------oOO--(_)--OOo-----------------------------------------------
Christof Bodner ***@***.***>
Linux - Life is too short for reboots
- First they ignore you. Then they laugh at you. Then they
fight you(*). Then you win. -- Ghandi
---------------------------------------------------------------------
email: ***@***.***
QTH: JN66WO
Signal: +43 650 7215383 (http://signal.org)
---------------------------------------------------------------------
GnuPG public key: 0xB15DA60F (http://wwwkeys.eu.pgp.net) Fingerprint 5222
4DEA 773A 60B3 22F9 D244 15EF 6645 B15D A60F
---------------------------------------------------------------------
|
This is related to the latest Overleaf Update and apparently not a bug. See overleaf/overleaf#1120 and the Release Notes. You can either use the Workaround from the release notes or the officially recommended method of using the Overleaf Toolkit. |
Edit the mongo:
restart: always
image: mongo:4.4
container_name: mongo
command: "--replSet overleaf"
expose:
- 27017
volumes:
- mongo_data:/data/db
healthcheck:
test: echo 'db.stats().ok' | mongo localhost:27017/test --quiet
interval: 10s
timeout: 10s
retries: 5
mongoinit:
image: mongo:4.4
# this container will exit after executing the command
restart: "no"
depends_on:
mongo:
condition: service_healthy
entrypoint:
[
"mongo",
"--host",
"mongo:27017",
"--eval",
'rs.initiate({ _id: "overleaf", members: [ { _id: 0, host: "mongo:27017" } ] })',
] the one time container should do the trick |
Thanks, now it works! :-) |
Describe the bug
the Mongoose service is not started
To Reproduce
Steps to reproduce the behavior:
docker compose start
Expected behavior
access to localhost:80 is possible
LOG-file
The text was updated successfully, but these errors were encountered: