Cribl Edge in Docker is erroring out

Tony Reinke - Cribl

I am trying to add a new Edge node to my Cribl Cloud instance. I click on the Add/Update Edge Node and get the script. The docker instance installs but when it goes to run the Edge instance, it errors out.

Server:
Ubuntu 22.04.3 LTS (GNU/Linux 5.2.0 x86_64)

Install:
docker run -d --privileged -e "CRIBL_DIST_MASTER_URL=tls://{token}@{instance}.cribl.cloud:4200?group=default_fleet" -e "CRIBL_DIST_MODE=managed-edge" -e "CRIBL_EDGE=1" -p 9420:9420 -v "/:/hostfs:ro" --restart unless-stopped --name "cribl-edge" cribl/cribl:latest
Unable to find image 'cribl/cribl:latest' locally
latest: Pulling from cribl/cribl
edaedc954fb5: Pull complete
f83a34600de3: Pull complete
94a7ecdae25d: Pull complete
995bcc02c181: Pull complete
b0adc0627ec2: Pull complete
Digest: sha256:8879de72b7cd95715e938d7828dd6adb0e5869fe893cfe1612cd520e0746bf46
Status: Downloaded newer image for cribl/cribl:latest
db13a2d0f898bca6a983e62458d736f573819b825b19fe1f78da1bfb4e107ac8

Error Message:
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: resulting devices cgroup doesn't match target mode: unknown.

Contain List:
docker container list -a
CONTAINER ID   IMAGE                COMMAND                  CREATED          STATUS                       PORTS                                       NAMES
db13a2d0f898   cribl/cribl:latest   "/sbin/entrypoint.sh…"   21 minutes ago   Created                      0.0.0.0:9420->9420/tcp, :::9420->9420/tcp   cribl-edge

Thoughts?

Tony Reinke - Cribl

Found out that docker sometimes doesn't like working with some VPS systems and my VPS provider uses Virtuozzo / OpenVZ 7. I was able to install the linux version of Edge on the system.

tmacdonald@cribl.io

This looks like it could be an issue with docker itself.

I would recommend starting up a simple docker container that is known to work. You could also try running docker version to see if the client is running the same docker version as the daemon.

This thread points to the issue being with an outdated kernel: https://github.com/docker/cli/issues/3481

Tony Reinke - Cribl

I currently have a mail server running on the server in Docker. I can also run the Hello World container. The server is up to date.

# uname -r


5.2.0

###

# docker run hello-world

Hello from Docker!


This message shows that your installation appears to be working correctly.


To generate this message, Docker took the following steps:


1. The Docker client contacted the Docker daemon.


2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64)


3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading


4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.


To try something more ambitious, you can run an Ubuntu container with:


$ docker run -it ubuntu bash


Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/


For more examples and ideas, visit:


https://docs.docker.com/get-started/

###

# docker ps -a
CONTAINER ID   IMAGE                COMMAND                  CREATED          STATUS                      PORTS                                       NAMES

1dff8e208520   hello-world          "/hello"                 30 seconds ago   Exited (0) 29 seconds ago                                               xenodochial_heyrovsky

db13a2d0f898   cribl/cribl:latest   "/sbin/entrypoint.sh…"   16 hours ago     Created                     0.0.0.0:9420->9420/tcp, :::9420->9420/tcp   cribl-edge

55695ab823dd   analogic/poste.io    "/init"                  21 hours ago     Up 17 hours (healthy)                                                   {server name}

####

# apt update                   

Hit:1 https://download.docker.com/linux/ubuntu jammy InRelease

Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                            

Get:3 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]                                                         

Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]                                         

Hit:5 http://archive.canonical.com/ubuntu jammy InRelease                                                       

Get:6 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [857 kB]       

Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1059 kB]

Get:8 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [175 kB]

Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [233 kB]              

Get:10 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [989 kB]

Get:11 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [216 kB]

Fetched 3758 kB in 2s (2376 kB/s)                                

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

All packages are up to date.

root@mail:~# apt upgrade

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

Calculating upgrade... Done

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Tony Reinke - Cribl

Found out that docker sometimes doesn't like working with some VPS systems and my VPS provider uses Virtuozzo / OpenVZ 7. I was able to install the linux version of Edge on the system.