AutoKuma icon indicating copy to clipboard operation
AutoKuma copied to clipboard

Using AutoKuma on Docker Standalone throws error

Open pxlfrk opened this issue 1 year ago • 1 comments

Hi all,

i am experimenting with AutoKuma on my current homelab setup:

  • Docker plain (Docker version 27.1.1, build 6312585)
  • both container (autokuma and uptimekuma are on the same docker-network (backend)
  • DockerHost is mounted to the autokuma-container via volume
  • i tried multiple autokuma tags, from 0.7.0 to 0.8.0 to master, the results where always the same

For my test i setup a compose-file with autokuma and a a hello-world-container. my uptimekuma-Container is running in a seaprate compose-stack. Both stacks are connected via the backend-network.

services:

  hello_world:
    image: hello-world
    labels:
      - uptimeautokuma.helloworld.http.name = HelloWorldTest
      - uptimeautokuma.helloworld.http.url = https://achimkraemer.com

  autokuma:
    image: ghcr.io/bigboot/autokuma:master
    restart: unless-stopped
    container_name: ${COMPOSE_PROJECT_NAME}_autokuma
    env_file: stack.env
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - npm
      - backend
    environment:
      AUTOKUMA__KUMA__URL: http://uptimekuma:3001
      AUTOKUMA__KUMA__USERNAME: ${AUTOKUMA__KUMA__USERNAME}
      AUTOKUMA__KUMA__PASSWORD: ${AUTOKUMA__KUMA__PASSWORD}
      AUTOKUMA__KUMA__CALL_TIMEOUT: 5
      AUTOKUMA__KUMA__CONNECT_TIMEOUT: 5
      AUTOKUMA__ON_DELETE: delete
      AUTOKUMA__TAG_NAME: AutoKuma
      AUTOKUMA__TAG_COLOR: "#6FE199"

      AUTOKUMA__DOCKER__LABEL_PREFIX: uptimeautokuma
      AUTOKUMA__DOCKER__SOURCE: Both
      AUTOKUMA__DEFAULT_SETTINGS: |-
        http.max_redirects: 10
        *.max_retries: 5
        *.interval: 120
        *.retry_interval: 120


networks:
  npm:
    external: true
    name: npm
  backend:
    external: true
    name: uptimekuma_backend

Regardless of how i create these stacks (plain compose run via shell, logged in as root), via Portainer WebEditor or as Portainer Git-Stack i always encounter this message in the logs:

WARN [autokuma::sync] Encountered error during sync: Docker responded with status code 503: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.

As far as i can tell from the docs, AutoKuma should be able to run on docker swarm as well as "plain" docker. Is there any misconfiguration in my setup/configuration or is this a bug in AutoKuma?

Thanks! 🥳

pxlfrk avatar Oct 07 '24 18:10 pxlfrk

Hi, you set AutoKuma to use both containers and services, but services are a swarm only thing, just remove this line: AUTOKUMA__DOCKER__SOURCE: Both

BigBoot avatar Oct 07 '24 23:10 BigBoot