simple example, what is wrong?

[helmut72]

I don't get it. Started with a simple example like from the docs:
https://doco.cd/latest/Deploy-Settings/#auto-discovery-settings

.doco-cd.yml

working_dir: apps/
auto_discovery:
  enabled: true
  depth: 1

apps/apache/compose.yml

services:
  apache:
    image: httpd:latest
    container_name: my-apache-app
    ports:
    - 2432:80

apps/apache2/compose.yml

services:
  apache2:
    image: httpd:latest
    container_name: my-apache-app-2
    ports:
    - 2433:80

docker ps -a | grep apache

root@server /docker/prepare/doco-cd $ docker ps -a |grep apache
021f7454a654   httpd:latest                                            "httpd-foreground"       11 minutes ago   Created                                                                                                                                                                                                                                                                                                                                                  my-apache-app-2
1d2e6e68cdcd   httpd:latest                                            "httpd-foreground"       11 minutes ago   Up 11 minutes             0.0.0.0:2432->80/tcp, [::]:2432->80/tcp                                                                                                                                                                                                                                                                                        my-apache-app

Log:

{
    "time": "2026-05-18T23:01:22.048444255+02:00",
    "level": "info",
    "msg": "polling repository",
    "job_id": "019e3ce4-b4ff-7bde-bc6c-cb4d96c51221",
    "repository": "example.com/test/doco-cd",
    "trigger": {
        "config": {
            "deployments": [],
            "interval": 60,
            "reference": "main",
            "run_once": false,
            "target": "",
            "url": "https://example.com/test/doco-cd.git"
        },
        "event": "poll"
    }
}
{
    "time": "2026-05-18T23:01:22.477262521+02:00",
    "level": "info",
    "msg": "deploying stack",
    "deploy": {
        "job_id": "019e3ce4-b4ff-7bde-bc6c-cb4d96c51221",
        "need_signal": null,
        "recreate": {
            "forced_services": [],
            "mode": "diverged"
        },
        "reference": "main",
        "repository": "example.com/test/doco-cd",
        "stack": "apache",
        "stage": "deploy"
    }
}
{
    "time": "2026-05-18T23:01:25.843897661+02:00",
    "level": "info",
    "msg": "deploying stack",
    "deploy": {
        "job_id": "019e3ce4-b4ff-7bde-bc6c-cb4d96c51221",
        "need_signal": null,
        "recreate": {
            "forced_services": [],
            "mode": "diverged"
        },
        "reference": "main",
        "repository": "example.com/test/doco-cd",
        "stack": "apache2",
        "stage": "deploy"
    }
}
{
    "time": "2026-05-18T23:01:28.090084498+02:00",
    "level": "error",
    "msg": "deployment failed",
    "deploy": {
        "error": "failed to deploy stack apache2: failed to deploy stack: 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: can't get final child's PID from pipe: EOF",
        "job_id": "019e3ce4-b4ff-7bde-bc6c-cb4d96c51221",
        "reference": "main",
        "repository": "example.com/test/doco-cd",
        "stack": "apache2"
    }
}
{
    "time": "2026-05-18T23:01:28.090385176+02:00",
    "level": "error",
    "msg": "error during poll job",
    "error": "deployment failed, err: failed to deploy stack apache2: failed to deploy stack: 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: can't get final child's PID from pipe: EOF",
    "job_id": "019e3ce4-b4ff-7bde-bc6c-cb4d96c51221",
    "repository": "example.com/test/doco-cd"
}
{
    "time": "2026-05-18T23:01:28.090617338+02:00",
    "level": "warning",
    "msg": "job completed with errors",
    "elapsed_time": "6.042s",
    "error": "deployment failed, err: failed to deploy stack apache2: failed to deploy stack: 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: can't get final child's PID from pipe: EOF",
    "job_id": "019e3ce4-b4ff-7bde-bc6c-cb4d96c51221",
    "next_run": "2026-05-18T23:02:28+02:00",
    "repository": "example.com/test/doco-cd"
}
{
    "time": "2026-05-18T23:02:28.092015447+02:00",
    "level": "info",
    "msg": "polling repository",
    "job_id": "019e3ce5-b6fb-7d2a-8ed8-6e8e86bc7dad",
    "repository": "example.com/test/doco-cd",
    "trigger": {
        "config": {
            "deployments": [],
            "interval": 60,
            "reference": "main",
            "run_once": false,
            "target": "",
            "url": "https://example.com/test/doco-cd.git"
        },
        "event": "poll"
    }
}
{
    "time": "2026-05-18T23:02:28.316696221+02:00",
    "level": "info",
    "msg": "job completed successfully",
    "elapsed_time": "224ms",
    "job_id": "019e3ce5-b6fb-7d2a-8ed8-6e8e86bc7dad",
    "next_run": "2026-05-18T23:03:28+02:00",
    "repository": "example.com/test/doco-cd"
}
{
    "time": "2026-05-18T23:03:28.317976712+02:00",
    "level": "info",
    "msg": "polling repository",
    "job_id": "019e3ce6-a23d-7dd3-aed5-5c81ae77d9b9",
    "repository": "example.com/test/doco-cd",
    "trigger": {
        "config": {
            "deployments": [],
            "interval": 60,
            "reference": "main",
            "run_once": false,
            "target": "",
            "url": "https://example.com/test/doco-cd.git"
        },
        "event": "poll"
    }
}
{
    "time": "2026-05-18T23:03:28.539488516+02:00",
    "level": "info",
    "msg": "job completed successfully",
    "elapsed_time": "221ms",
    "job_id": "019e3ce6-a23d-7dd3-aed5-5c81ae77d9b9",
    "next_run": "2026-05-18T23:04:28+02:00",
    "repository": "example.com/test/doco-cd"
}
{
    "time": "2026-05-18T23:04:28.543981056+02:00",
    "level": "info",
    "msg": "polling repository",
    "job_id": "019e3ce7-8d7f-7c4f-9aca-6826d4715de9",
    "repository": "example.com/test/doco-cd",
    "trigger": {
        "config": {
            "deployments": [],
            "interval": 60,
            "reference": "main",
            "run_once": false,
            "target": "",
            "url": "https://example.com/test/doco-cd.git"
        },
        "event": "poll"
    }
}
{
    "time": "2026-05-18T23:04:28.937110798+02:00",
    "level": "info",
    "msg": "job completed successfully",
    "elapsed_time": "393ms",
    "job_id": "019e3ce7-8d7f-7c4f-9aca-6826d4715de9",
    "next_run": "2026-05-18T23:05:28+02:00",
    "repository": "example.com/test/doco-cd"
}

But doesn't work. One Apache never starts. What is wrong? Both started without any problems without doco-cd, using docker compose up -d

Thanks

[kimdre]

Seems like a bug with the docker daemon, not with doco-cd. Can you remove the affected container and let doco-cd deploy again?
If the issue persists, try to check for this error via google. Maybe you can find a solution but this is not something that is related to doco-cd.

failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF

[helmut72]

Strange, it works directly on the server and I've a lot of containers running without any problems:

root@server /docker/prepare/doco-cd $ docker ps | wc -l
31

Also two containers using the Docker socket, Traefik and Portainer.

But anyway, I'll search tomorrow. Thanks.

Edit: I read your link. I use Ubuntu 22 on a Raspberry, it's not Kernel 4.x, but 5.x

Edit2:

Can you remove the affected container and let doco-cd deploy again?

I've tried several times on Sunday and this evening, of course removed the containers with docker rm -f

[kimdre]

Maybe you hit the maximum number of user namespaces.

https://stackoverflow.com/questions/64990279/docker-error-process-linux-go319-getting-the-final-childs-pid-from-pipe-cause

See also: moby/moby#40835

[helmut72]

Thanks, but I don't have any problems running docker run .. or docker compose up -d:

root@server /docker/prepare/test-apache $ tree .
.
├── apache3
│   └── compose.yml
└── apache4
    └── compose.yml

2 directories, 2 files
root@server /docker/prepare/test-apache $ cat */compose.yml
services:
  apache3:
    image: httpd:latest
    container_name: my-apache-app-3
    ports:
    - 2434:80
services:
  apache4:
    image: httpd:latest
    container_name: my-apache-app-4
    ports:
    - 2435:80
root@server /docker/prepare/test-apache $ cd apache3;docker compose up -d;cd ../apache4;docker compose up -d
[+] up 2/2
 ✔ Network apache3_default   Created                                                                                                                                           0.3s
 ✔ Container my-apache-app-3 Started                                                                                                                                           2.6s
[+] up 2/2
 ✔ Network apache4_default   Created                                                                                                                                           0.4s
 ✔ Container my-apache-app-4 Started                                                                                                                                           2.8s

If doco-cd is running, the example above don't work anymore and I get the same error. But only if doco-cd is running:

root@server /docker/prepare/test-apache $ cd apache3;docker compose up -d;cd ../apache4;docker compose up -d
[+] up 0/1
 ⠙ Container my-apache-app-3 Starting                                                                                                                                          2.2s
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: can't get final child's PID from pipe: EOF
[+] up 1/2
 ✔ Network apache4_default   Created                                                                                                                                           0.5s
 ⠴ Container my-apache-app-4 Starting                                                                                                                                          4.5s
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: can't get final child's PID from pipe: EOF

Looks like doco-cd change something when it's running. Don't get me wrong, I don't want to say the cause is doco-cd, but it change something. Ok, enough for this evening.

[kimdre]

Can you create more than 2 additional containers when doco-cd is not running? Looks to me like you are very close to the limit and since the doco-cd container is not running in your example you have a little more namespaces available.
Doco-CD doesn't do any magic in the background. In the end it just parses your docker compose files and sends the generated data to the docker API. Everything else after that is done by the Docker daemon/host.

[helmut72]

OMG, you are right!

root@server /docker/prepare/test-apache $ for i in $(seq 1 9);do docker compose -f ./apache$i/compose.yml up -d;done
[+] up 2/2
 ✔ Network apache1_default   Created                                                                                                                                           0.4s
 ✔ Container my-apache-app-1 Started                                                                                                                                           3.2s
[+] up 1/1
 ✔ Container my-apache-app-2 Started                                                                                                                                           3.8s
[+] up 1/2
 ✔ Network apache3_default   Created                                                                                                                                           0.6s
 ⠙ Container my-apache-app-3 Starting                                                                                                                                          3.2s
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: can't get final child's PID from pipe: EOF
[+] up 1/2
 ✔ Network apache4_default   Created                                                                                                                                           0.4s
 ⠧ Container my-apache-app-4 Starting                                                                                                                                          1.7s
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: can't get final child's PID from pipe: EOF
(...)

Can't believe it, because I did a cleanup few days before and my production system runs a lot more container/networks. This Raspi is my dev/test device.

Ok, thank you very much!