Problem
I use the docker container "any-sync-bundle:1.4.3-2026-04-21"
I would like to properly backup/dump the inside container mongoDB database ; unfortunately I don't manage to do it, wether I try inside or outside the container :
- inside : the mongodump doesn't seem to be installed
- outside : it seems that even if the port 27017 is exposed on the host, the listening adress of mongo (127.0.0.1:27017) doesn't allow to accept external connection (should be 0.0.0.0:27017?)
thierry@hpg3:/opt/anytypesync$ mongodump --host 127.0.0.1 --port 27017 --out /tmp/test-backup 2026-05-21T10:03:49.680+0200 Failed: can't create session: failed to connect to mongodb://127.0.0.1:27017/: server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: 127.0.0.1:27017, Type: Unknown, Last error: connection(127.0.0.1:27017[-61]) incomplete read of message header: read tcp 127.0.0.1:60742->127.0.0.1:27017: read: connection reset by peer: connection(127.0.0.1:27017[-61]) incomplete read of message header: read tcp 127.0.0.1:60742->127.0.0.1:27017: read: connection reset by peer }, ] }
Proposal
I understand the container should be the lightest as possible, so I maybe the second option (external backup/dump) would be better ; in that case would it be possible the make the mongo answering to external connection?
Additionally, I think it could also allow the anysync bundle's mongo instance monitoring from an external tool like Uptime Kuma (via its specific mongo monitor)
Alternatives considered
Maybe I missed something and there is already an existing way to properly backup the DB without stopping the bundle/sync service
Additional context
I am running the container on a Debian 13 AMD64 architecture.
Anyway, thank you for the great job already done with this bundle!
Very useful and reliable so far.
Thierry
Problem
I use the docker container "any-sync-bundle:1.4.3-2026-04-21"
I would like to properly backup/dump the inside container mongoDB database ; unfortunately I don't manage to do it, wether I try inside or outside the container :
thierry@hpg3:/opt/anytypesync$ mongodump --host 127.0.0.1 --port 27017 --out /tmp/test-backup 2026-05-21T10:03:49.680+0200 Failed: can't create session: failed to connect to mongodb://127.0.0.1:27017/: server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: 127.0.0.1:27017, Type: Unknown, Last error: connection(127.0.0.1:27017[-61]) incomplete read of message header: read tcp 127.0.0.1:60742->127.0.0.1:27017: read: connection reset by peer: connection(127.0.0.1:27017[-61]) incomplete read of message header: read tcp 127.0.0.1:60742->127.0.0.1:27017: read: connection reset by peer }, ] }Proposal
I understand the container should be the lightest as possible, so I maybe the second option (external backup/dump) would be better ; in that case would it be possible the make the mongo answering to external connection?
Additionally, I think it could also allow the anysync bundle's mongo instance monitoring from an external tool like Uptime Kuma (via its specific mongo monitor)
Alternatives considered
Maybe I missed something and there is already an existing way to properly backup the DB without stopping the bundle/sync service
Additional context
I am running the container on a Debian 13 AMD64 architecture.
Anyway, thank you for the great job already done with this bundle!
Very useful and reliable so far.
Thierry