[caasp-beta] Strange behaviour docker CAASP v3 beta 1
Le Bihan Stéphane (AMUNDI-ITS)
stephane.lebihan at amundi.com
Thu May 24 09:25:17 MDT 2018
Hi Valentin,
Sorry i made mistake on thread.... :s
Thanks for your response.
I join to mail.
One with mistake thread on mailing beta. Who I explain support config is stuck on Docker test.
One with thread with other user of CAASP plateform here.
I copy and modified supportconfig for don't make test "docker top" or docker log because supportconfig stuck on their command.
Here diff on two file :
dl360o-101:~ # diff supportconfig /sbin/supportconfig
2826,2831c2826,2831
< #for i in $(docker ps -a 2>/dev/null | grep -v "COMMAND" | awk '{print $1}');
< #do
< # log_cmd $OF "docker top $i"
< # log_cmd $OF "docker logs $i"
< # log_cmd $OF "docker inspect $i"
< #done
---
> for i in $(docker ps -a 2>/dev/null | grep -v "COMMAND" | awk '{print $1}');
> do
> log_cmd $OF "docker top $i"
> log_cmd $OF "docker logs $i"
> log_cmd $OF "docker inspect $i"
> done
Example of stuck :
dl360o-101:~ # docker ps -a | grep 843c6dd27ae7
843c6dd27ae7 sles12/pause:1.0.0 "/usr/share/suse-d..." 7 hours ago Created k8s_POD_influxtreon-1527151380-b879p_tick_7aafe27b-5f2e-11e8-8f7c-525400cfa2b7_1
dl360o-101:~ # /usr/bin/docker logs 843c6dd27ae7
(Nothing, I stop with ^C)
dl360o-101:~ # /usr/bin/docker inspect 843c6dd27ae7
^C
I can't open bug on SCC for Beta program, just for SLES12 Entreprise Server and I don't find how open issue in bugzilla.
How or where I can put supportconfig for you ?
Regards,
Stéphane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com
@: sits.unix at amundi.com
Visit us on:
-----Message d'origine-----
De : Valentin Rothberg [mailto:vrothberg at suse.com]
Envoyé : jeudi 24 mai 2018 14:07
À : Le Bihan Stéphane (AMUNDI-ITS)
Cc : caasp-beta at lists.suse.com
Objet : Re: [caasp-beta] Strange behaviour docker CAASP v3 beta 1
Hi,
thanks a lot for reaching out to us.
On May/24/18 10:04, Le Bihan Stéphane (AMUNDI-ITS) wrote:
[...]
> Error response from daemon: rpc error: code = Unknown desc =
> containerd: container not found
>
> I don't understand why container is not destroyed. Have you any idea ?
Similar issues usually happen when processes inside the containers are not properly shutdown (e.g., when the system runs out of memory or when a process has forcefully been killed for any other reason). In addition to steps mentioned below, may I ask how much RAM the node you extracted the logs above from has?
This is hard to say without looking at the logs. If possible, could you provide a supportconfig for us to have a first glimpse at your issue?
Feel free to open a bug or upload the logs somewhere reachable for us as described here [1].
Kind regards,
Valentin
[1] https://www.suse.com/c/free_tools/supportconfig-linux/
-------------- next part --------------
An embedded message was scrubbed...
From: =?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=
<stephane.lebihan at amundi.com>
Subject: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2?
Date: Thu, 24 May 2018 13:39:45 +0000
Size: 21724
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180524/c75657e0/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: "Chesnoy Bernard (AMUNDI-ITS)" <bernard.chesnoy at amundi.com>
Subject: RE: [caasp-beta] Strange behaviour docker CAASP v3 beta 1
Date: Thu, 24 May 2018 13:37:38 +0000
Size: 20968
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180524/c75657e0/attachment-0001.eml>
More information about the caasp-beta
mailing list