Bug: Monerod crashes on Docker for no reason
Monerod crashes on Docker for no reason, with no warning and anything useful in logs. I am trying to host a public node on my Docker Swarm infrastructure.

Examples of log outputs:

```2023-12-24 03:13:36.400	I Synced 1224020/3046366 (40%, 1822346 left)
2023-12-24 03:13:36.402	I [batch] DB resize needed
2023-12-24 03:15:39.304	I LMDB Mapsize increased.  Old: 10613MiB, New: 12070MiB
2023-12-24 03:15:40.489	I Synced 1224120/3046366 (40%, 1822246 left, 8% of total synced, estimated 19.3 hours left)
2023-12-24 03:15:40.833	I Synced 1224220/3046366 (40%, 1822146 left)
2023-12-24 03:15:41.074	I Synced 1224320/3046366 (40%, 1822046 left)
2023-12-24 03:15:41.549	I Synced 1224420/3046366 (40%, 1821946 left)
2023-12-24 03:15:42.012	I Synced 1224520/3046366 (40%, 1821846 left)
2023-12-24 03:15:42.258	I Synced 1224620/3046366 (40%, 1821746 left)
2023-12-24 03:15:42.762	I Synced 1224720/3046366 (40%, 1821646 left)
2023-12-24 03:15:43.287	I Synced 1224820/3046366 (40%, 1821546 left)
2023-12-24 03:15:43.347	I Synced 1224840/3046366 (40%, 1821526 left)
2023-12-24 03:15:43.400	I Synced 1224860/3046366 (40%, 1821506 left)
2023-12-24 03:15:43.448	I Synced 1224880/3046366 (40%, 1821486 left)
2023-12-24 03:15:43.500	I Synced 1224900/3046366 (40%, 1821466 left)
2023-12-24 03:15:43.545	I Synced 1224920/3046366 (40%, 1821446 left)
2023-12-24 03:15:43.783	I Synced 1224940/3046366 (40%, 1821426 left)
2023-12-24 03:15:43.843	I Synced 1224960/3046366 (40%, 1821406 left)
2023-12-24 03:15:44.114	I p2p net loop stopped
2023-12-24 03:15:46.235	I Stopping core RPC server...
2023-12-24 03:15:46.309	I Stopping restricted RPC server...
2023-12-24 03:15:46.309	I Node stopped.
2023-12-24 03:15:46.409	I Deinitializing core RPC server...
2023-12-24 03:15:51.718	I Deinitializing restricted RPC server...
2023-12-24 03:15:51.982	I Deinitializing p2p...
2023-12-24 03:15:52.593	I Deinitializing core...
```

Then it starts again from 0. I've also seen something like this:

```
2023-12-24 21:26:20.599	I Synced 3014544/3046895 (98%, 32351 left, 63% of total synced, estimated 54.6 minutes left)
2023-12-24 21:26:24.455	I Synced 3014564/3046895 (98%, 32331 left)
2023-12-24 21:26:28.785	I Synced 3014584/3046895 (98%, 32311 left)
2023-12-24 21:26:30.740	I Synced 3014604/3046895 (98%, 32291 left)
2023-12-24 21:26:35.716	I Synced 3014624/3046895 (98%, 32271 left)
2023-12-24 21:26:38.341	I Synced 3014644/3046895 (98%, 32251 left)
2023-12-24 21:26:38.465	E Error in handle_invoke_map: boost::bad_get: failed value get using boost::get
```

I first thought it was something to do with gluster FS or one of Docker Swarm nodes. So I ran it on local disk and pinned to a particular VM. The VM has 2 cores on pretty unused 7700x VM and disk on 980 Pro NVMe SSD, with lots of capacity free. I also tried running it on a node with 8 GB RAM and almost all of 6 core CPU.

This is my Docker Compose file:

```
version: '3.3'

services:
  monerod:
    image: sethsimmons/simple-monerod:latest
    user: 0:0
    volumes:
      - /home/varun/monero/bitmonero:/home/monero/.bitmonero
    deploy:
      labels:
        homepage.group: Services
        homepage.name: Monero
        homepage.description: Monero Public Node
        homepage.icon: monero.png
        homepage.href: https://monero.ca.varunpriolkar.com
        homepage.server: docker
        homepage.statusStyle: dot
      mode: replicated
      replicas: 1
      placement:
        constraints:
          - node.hostname == docker-4
    networks:
      - monero
    ports:
      - target: 18080
        published: 18080
        protocol: tcp
        mode: host
      - target: 18089
        published: 18089
        protocol: tcp
        mode: host
    expose:
      - "18080"
      - "18081"
      - "18089"
    command:
      - "--rpc-restricted-bind-ip=0.0.0.0"
      - "--rpc-restricted-bind-port=18089"
      - "--rpc-bind-ip=0.0.0.0"
      - "--confirm-external-bind"
      - "--public-node"
      - "--no-igd"
      - "--enable-dns-blocklist"
      - "--prune-blockchain"
  tor:
    image: goldy/tor-hidden-service:latest
    environment:
        MONEROD_TOR_SERVICE_HOSTS: 18089:monerod:18089
        MONEROD_TOR_SERVICE_VERSION: '3'
    volumes:
      - /mnt/vol1/monero/tor:/var/lib/tor/hidden_service/
    networks: 
      - monero
    deploy:
      mode: replicated
      replicas: 1
      placement:
        constraints:
          - node.hostname != rpi
  gui:
    image: hvalev/monero-dashboard:latest
    networks:
      - monero
      - caddy
    environment:
      MONERO_HOST: monerod
      MONERO_PORT: 18081
      TICKER: "true"
      PORT: 3333
    deploy:
      mode: replicated
      replicas: 1
      labels:
        caddy: "monero.ca.varunpriolkar.com"
        caddy.reverse_proxy.to: "{{upstreams 3333}}"
        caddy.tls.dns: "route53"
        caddy.tls.dns.access_key_id: "{env.AWS_ACCESS_KEY}"
        caddy.tls.dns.secret_access_key: "{env.AWS_SECRET_KEY}"
 
networks:
  caddy:
    external: true
  monero:
    driver: overlay
    attachable: true
   ```

I first thought it could be something to do with the specific Docker image I am using, but I came across something similar: https://stackoverflow.com/questions/77603054/monero-daemon-in-docker-container-exits-for-no-reason

If you need any more information, let me know.