v4 macOS Docker Fails to start with CRITICAL -- Cannot init the curses library

[shamoon]

Apologies if Im missing something obvious here, I just wanted to test out v4 so I can ensure compatibility with a tool I work on when v4 is released but I cant get the container to start on macOS 14.4 (23E214) on M2 Pro MBP, the container exits with:

2024-03-28 08:43:25 2024-03-28 06:43:25,049 -- INFO -- Start Glances 4.0.0_beta01
2024-03-28 08:43:25 2024-03-28 06:43:25,049 -- INFO -- CPython 3.11.4 (/venv/bin/python3) and psutil 5.9.8 detected
2024-03-28 08:43:25 2024-03-28 06:43:25,051 -- INFO -- Read configuration file '/etc/glances/glances.conf'
2024-03-28 08:43:25 2024-03-28 06:43:25,108 -- INFO -- Start GlancesStandalone mode
2024-03-28 08:43:25 2024-03-28 06:43:25,177 -- ERROR -- containers (Podman) plugin - Can't connect to Podman (http://%2Frun%2Fuser%2F1000%2Fpodman%2Fpodman.sock/v5.0.0/libpod/_ping (HEAD operation failed))
2024-03-28 08:43:27 Cannot init the curses library (setupterm: could not find terminal)
2024-03-28 08:43:27 2024-03-28 06:43:27,237 -- CRITICAL -- Cannot init the curses library (setupterm: could not find terminal)

My compose is pretty simple:

  glancesv4:
    image: nicolargo/glances:dev
    container_name: glancesv4
    pid: host
    privileged: true
    network_mode: host
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - TZ=America/Los_Angeles

The only issue I found that seemed similar was #2589 but unlike that one I do want to use the webui. Appreciate any help, love the project!

[nicolargo]

Hi @shamoon

try to add the following option to your Docker compose:

stdin_open: true   # docker run -i
tty: true          # docker run -t

[shamoon]

Amazing, thank you! Apologies if I missed that in the docs.

[nicolargo]

No, the version 4 did not expose the RestAPI by default. It's exactly the same behavor than the version 3.