Shutting down instance takes a while #24
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Maybe related to Benjamin_Loison/moby/issues/2.
On OverClock3000.
Should measure with
time
.Related to #7.
https://docs.docker.com/compose/install/linux/#install-using-the-repository
https://docs.docker.com/engine/install/debian/#install-using-the-repository
After replacing in
config/overleaf.rc
:with:
overleaf/wiki/Release-Notes-5.x.x#redis-aof-persistence-enabled-by-default
overleaf/wiki/Data-and-Backups/#redis
https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/#how-i-can-switch-to-aof-if-im-currently-using-dumprdb-snapshots
After adding
REDIS_AOF_PERSISTENCE=true
toconfig/overleaf.rc
:a61d9ebff5/lib/docker-compose.base.yml (L2)
a61d9ebff5/lib/docker-compose.vars.yml (L2)
a61d9ebff5/lib/docker-compose.redis.yml (L2)
a61d9ebff5/lib/docker-compose.mongo.yml (L2)
are the latest version and still mention
version
.https://www.overleaf.com and https://www.overleaf.com/login were responding but not logging in and https://www.overleaf.com/projects
does not return anything.
Both overleaf/issues and overleaf/toolkit/issues do not return any issue for
MongoNetworkError
.Maybe related to the Stack Overflow question 46523321.
If replace:
with:
then get:
Source: https://docs.docker.com/reference/cli/docker/image/pull/
does not return anything interesting.
https://hub.docker.com/r/sharelatex/sharelatex
https://hub.docker.com/r/sharelatex/sharelatex/tags
https://hub.docker.com/u/sharelatex does not showcase any other interesting docker image.
Maybe it is a one minute timer to prevent users that the instance will shut down?
minute does not seem to return any interesting issue in both overleaf/issues and overleaf/toolkit/issues.
does not return anything.
Following Benjamin_Loison/overleaf/issues/25#issuecomment-2112:
Maybe there is not this delay if there is nobody using the instance.
So
bin/up
can be instantly stopped thanks to ctrl + c while it does not seem possible withbin/start
orbin/up -d
.