Dragonfly DB exits with error code 132

[sargon64]

To reproduce, run a docker compose instance with the following compose.yml file:

version: '3.8'
services:
  dragonfly:
    image: 'docker.dragonflydb.io/dragonflydb/dragonfly'
    ulimits:
      memlock: -1
    ports:
      - "6379:6379"
    # For better performance, consider `host` mode instead `port` to avoid docker NAT.
    # `host` mode is NOT currently supported in Swarm Mode.
    # https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode
    # network_mode: "host"
    volumes:
      - dragonflydata:/data
volumes:
  dragonflydata:

Environment:

• OS: ubuntu 22.04
• Kernel: 5.15.0-78-generic
• Containerized: Docker Compose
• Dragonfly Version: 1.7.1

[romange]

well, it works for me. I think the problem is with your hardware. Do you run it on your laptop?

[ChecksumDev]

I can confirm this happens on any operating system I have tried, from latest clean install of Ubuntu LTS to windows running the docker using compose or docker run results in the same failure.

Though I've only ever observed the status code when deploying with Portainer.
My setup is running docker inside of Proxmox under KVM.

[sargon64]

I still cannot run dragonfly after re-pulling today. I am running dragonfly under docker engine 24.0.5 under alpine 3.18.2 under VMWare ESXi on a Xeon Silver 4400 Processor with 128Gb of dedicated RAM.

[romange]

@sargon64 you must change the settings on your VMWare to enable extended CPU flags (skylake architecture).

[sargon64]

I had that enabled. It seems @ChecksumDev is having the same issue on proxmox?

[WooMai]

In Proxmox VE, you should set the CPU type to host. I had the same issue before. kvm64 might be missing some CPU Flags.