Netdata not showing docker container stats

[Chheung]

OS: Ubuntu 22
Machine: AWS EC2 & DigitalOcean Droplet

Steps:

1. Follow caprover document installation

[githubsaturn]

Are you using snap installation of Docker or official installation? Can you run this script and paste the output here?

# Check for Snap installation
if snap list docker &>/dev/null; then
    echo "Docker is installed via Snap"
    exit 0
fi

# Check for APT installation
if dpkg -l | grep -q docker.io; then
    echo "Docker is installed via APT (docker.io)"
    exit 0
elif dpkg -l | grep -q docker-ce; then
    echo "Docker is installed via APT (docker-ce)"
    exit 0
fi

# Check for known Snap-related bugs (e.g., cgroup paths, overlayfs issues)
if docker info 2>/dev/null | grep -q "docker snap"; then
    echo "Docker appears to be installed via Snap (inferred from Docker info)"
    exit 0
fi

[githubsaturn]

This issue was reported by someone else recently too
caprover/caprover#2289

[Chheung]

Are you using snap installation of Docker or official installation? Can you run this script and paste the output here?

# Check for Snap installation
if snap list docker &>/dev/null; then
    echo "Docker is installed via Snap"
    exit 0
fi

# Check for APT installation
if dpkg -l | grep -q docker.io; then
    echo "Docker is installed via APT (docker.io)"
    exit 0
elif dpkg -l | grep -q docker-ce; then
    echo "Docker is installed via APT (docker-ce)"
    exit 0
fi

# Check for known Snap-related bugs (e.g., cgroup paths, overlayfs issues)
if docker info 2>/dev/null | grep -q "docker snap"; then
    echo "Docker appears to be installed via Snap (inferred from Docker info)"
    exit 0
fi

Okay will do tonight. I think this is related to Ubuntu 22 using cgroup v2

[Chheung]

This issue was reported by someone else recently too caprover/caprover#2289

I got

Docker is installed via APT (docker-ce)

[githubsaturn]

did you use the default CapRover droplet on digital ocean?
https://marketplace.digitalocean.com/apps/caprover

Also, can you provide an example droplet without any sensitive information and send the ip and root password to support at caprover dot com?

[Chheung]

did you use the default CapRover droplet on digital ocean? https://marketplace.digitalocean.com/apps/caprover

Also, can you provide an example droplet without any sensitive information and send the ip and root password to support at caprover dot com?

sorry for late reply, no and sorry that i can not provide any sensitive info such as ip and password.

However, i've tried on AWS EC2 ubuntu 22 and 24 both doesnt seem to work.

[Chheung]

I did the installation by
https://caprover.com/docs/get-started.html

And docker from https://docs.docker.com/engine/install/ubuntu/

[githubsaturn]

Let's see if we can narrow this down:

• Try creating an instance using this image: https://marketplace.digitalocean.com/apps/caprover
• DO NOT run apt update etc, just use this image
• DO NOT run caprover serversetup
• Log in to the web UI, and assign the root domain to be 192-168-1-250.nip.io (replace 192-168-1-250 with the IP of the machine)
• DO NOT enable HTTPS
• Go to monitoring and enable NetData
• Go to Apps and create a new app (test-app)
• Go to Netdata (after waiting at least 30sec since you enabled it) and check to see if you can see the container information.

Follow these steps (do not change the order) and see if you can reproduce the issue.

PS: nip.io is a free service that maps any IP to a domain name but it does not support HTTPS.

[Chheung]

@githubsaturn
it works

[githubsaturn]

Perfect! Now that you have a working version and a non-working version, all you need to do is to bisect to find the problem:

Run caprover serversetup to properly attach a domain and enable HTTPS
Turn off Netdata, wait for 30sec, and turn it back on again.
Wait for another 30sec
Does it still work? If so, move on to the next step:

Run apt update && apt full-upgrade
Turn off Netdata, wait for 30sec, and turn it back on again.
Wait for another 30sec
Does it still work? If so, then, move on to the next step:

• Compare the docker version / linux version / etc between the working and non-working version (on DigitalOcean)

PS: AWS not working could be because of their custom OS kernels, so stick to DitigalOcean to find out what causes the issue to appear.

[Chheung]

okay will do after a few days!