Container Health & Warning

[DoingBobThings 0]

Howdy, folks.  Long time Emby user, just migrated to a UGREEN 4800 and have been having a crash course in Docker.

I have Emby server up and running, but wanted to add a Health Check statement to the compose file.  It seems to be working but I have a red dot indicating a problem.  Taking a deeper dive (using Dockhand) I came across this.  Could this be the issue?  If so, I have no idea how to correct it.  I'd be grateful for some help to point me in the right direction.

Thanks in advance!

 

services:
  emby:
    image: emby/embyserver:latest
    container_name: emby

    restart: unless-stopped

    network_mode: bridge

    ports:
      - "8096:8096"
      - "8920:8920"

    environment:
      - UID=1000
      - GID=10
      - TZ=America/New_York

    devices:
      - /dev/dri:/dev/dri

    healthcheck:
      test: ["CMD", "curl", "-f", "http://xxx.xxx.x.xxx:8096"]
      interval: 1m30s
      timeout: 10s
      retries: 3
      start_period: 30s 

    volumes:
      # Emby application data
      - /volume1/Docker/Emby/config:/config
      - /volume1/Docker/Emby/cache:/cache
#      - /volume1/Docker/Emby/transcode:/transcode

      # Shared media (read only)
      - /volume1/Media:/media:ro

 

Edited 1 hour ago by DoingBobThings
spelling error

[Lessaj 511]

I would do the health check as http://xxx.xxx.x.xxx:8096/System/Ping instead.

[DoingBobThings 0]

Updated with:

    healthcheck:
      test: ["CMD", "curl", "-f", "http://192.168.1.100:8096/System/Ping"]
      interval: 1m30s
      timeout: 10s
      retries: 3
      start_period: 30s 

However the issue with the red warning still remains.

[Lessaj 511]

Sorry, not familiar with this tool. What does the Health tab show? I doubt Layers has anything to do with it.

[DoingBobThings 0]

LOL

Yeah, it'd probably be a good idea to check that, I suppose. 

OCI runtime exec failed: exec failed: unable to start container process: exec: "curl": executable file not found in $PATH: unknown