Docker errors when trying to deploy Uptime Kuma

Hello,

I am a bit of a novice when it comes to container tech overall but please try to ignore that :smiley:

I am basically trying to deploy Uptime Kuma, it is like a monitoring tool but after running the docker compose file this error spits out and I am unable to figure out why.

The docker compose file is here (basically the copy/pasted example from their site):

version: "3.8"

services:
  uptime-kuma:
    image: louislam/uptime-kuma:latest
    container_name: uptime-kuma
    restart: always
    ports:
      - "3001:3001"  # This maps the container port "3001" to the host port "3001"
    volumes:
      - /path/to/data:/app/data  # Configuring persistent storage
    environment:
      - TZ=UTC  # Set the timezone (change to your preferred local timezone so monitoring times are the same)
      - UMASK=0022  # Set your file permissions manually
    networks:
      - kuma_network  # add your own custom network config
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:3001"]
      interval: 30s
      retries: 3
      start_period: 10s
      timeout: 5s
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: "3"

networks:
  kuma_network:
    driver: bridge
ERROR: for uptime-kuma  Cannot start service uptime-kuma: OCI runtime create failed: 
container_linux.go:380: starting container process caused: exec: "node": executable file not found in $PATH: unknown

Is anyone able to please point me in the right direction? Thank you.

1 Like

From what I can tell, it is to do with the image? but that image looks correct in the docker compose file above.

Did you try a docker compose pull to ensure the latest image?

Doesnโ€™t it automatically pull the latest one from that file? I will try and report back.

Plain docker run and docker compose up (without additional command line arguments) will not pull again, if a image with the same tag already exists.

When using tag latest, you should pull, when you want to update the image to the real latest one.

1 Like

Ah I see where I was going wrong lol :headstone:, It now made sense! Thank you.