Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCI runtime start failed: container process is already dead: unknown" OCI Runtime start failed: Container process is already dead: unknown" #2994

Open
kubecto opened this issue May 13, 2024 · 2 comments
Labels
kind/unconfirmed-bug-claim Unconfirmed bug claim

Comments

@kubecto
Copy link

kubecto commented May 13, 2024

Description

sudo /usr/local/bin/nerdctl run -d --name istcs-prometheus-config-reloader \
--restart=always \
-v "/mnt/plugins"/prometheus/conf:/etc/config:ro \
"10.102.26.195/monitoring_containers/prometheus-config-reloader:v0.65.1" \
--watch-interval=5s \
--reload-timeout=2s \
--watched-dir=/etc/config \
- reload - url = http://10.102.26.195: "9090" / - / reload

When I go to run when the time, but not seen running late, and the problem about: docker/for-linux#647, not sure what causes it

Steps to reproduce the issue

Run the above command, which runs a prometheus and a reload container

sudo /usr/local/bin/nerdctl run -d --name istcs-prometheus-server \
--restart=always \
--net=host \
-p "9090":9090 \
-v "/mnt/plugins"/prometheus/conf:/etc/config \
-v "/mnt/plugins"/prometheus/rules:/etc/config/rules \
-v "/mnt/plugins"/prometheus/data:/data \
-v "/mnt/plugins"/prometheus/prome-tokens:/etc/prome-tokens:ro \
"10.102.26.195 / monitoring_containers/Prometheus: v2.44.0 \"
--storage.tsdb.retention.time=90d \
--config.file=/etc/config/prometheus.yml \
--storage.tsdb.path=/data \
--web.listen-address="0.0.0.0:9090" \
--web.console.libraries=/etc/prometheus/console_libraries \
--web.console.templates=/etc/prometheus/consoles \
--web.enable-lifecycle \
--web.enable-admin-api \
--query.max-concurrency=100

Find a docker hub image and try to use the same image, here I changed to my private image repository address

Describe the results you received and expected

Expect no such error, which I found once

What version of nerdctl are you using?

nerdctl -v
nerdctl version 1.7.3
[root@localhost script-rollback]# runc -v
runc version 1.1.12
commit: v1.1.12-0-g51d5e946
spec: 1.0.2-dev
go: go1.20.13
libseccomp: 2.5.4
[root@localhost script-rollback]# containerd -v
containerd github.com/containerd/containerd v1.7.13 7c3aca7a610df76212171d200ca3811ff6096eb8

Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

Host information

cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
 uname  -a
Linux localhost.localdomain 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
@kubecto kubecto added the kind/unconfirmed-bug-claim Unconfirmed bug claim label May 13, 2024
@apostasie
Copy link
Contributor

@kubecto could you provide a simple way to reproduce this?

Obviously, we do not have access to your private registry.

What about you push these images on the hub?

@kubecto
Copy link
Author

kubecto commented May 20, 2024

At present, this problem has disappeared, when this problem occurs again, I will push it, thank you, I can leave this problem on for the time being

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/unconfirmed-bug-claim Unconfirmed bug claim
Projects
None yet
Development

No branches or pull requests

2 participants