Docker Containers Restarting (132), Istruzione illegale (core dumped)

Question

Docker Containers Restarting (132), Istruzione illegale (core dumped)

3

879 2019-03-05

Miimbatto costantementein uno show-stopper con alphanete docker su Ubuntu. Sospetto che sia qualcosa chetrascuro costantemente durante la configurazione. Imiei contenitori Dockerfunzionano soloper uno o due secondie poi si riavviano (132).

Alcuni scherzimi portano a credere che ricominciano dalpanico quasi subito.

Hoprovato Ubuntu 16.04. 18.04,virtualBox MVe vmWaree persino AMDe Intel. 4-6processorie 4-8 GB di RAM. Il risultato è sempre lo stesso.

Altri contenitori Dockerfunzionano senzaproblemi.

 $ docker version
Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:47 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.3
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       774a1f4
  Built:            Thu Feb 28 05:59:55 2019
  OS/Arch:          linux/amd64
  Experimental:     false

$ docker-compose version
docker-compose version 1.17.1, build unknown
docker-py version: 2.5.1
CPython version: 2.7.15rc1
OpenSSL version: OpenSSL 1.1.0g  2 Nov 2017

Ecco un'immaginenel casoin cui aiuti.

Ecco un log docker rappresentativo di un container:

 tezos@rob-VirtualBox:~$ docker logs alphanet_node_1
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...

Sareimoltogratoper qualsiasipensiero o suggerimento.

I'm consistently running into a show-stopper with alphanet and docker on ubuntu. I suspect it's something I consistently overlook when setting up. My docker containers only run for a second or two and then restart (132).

Some poking around leads me to believe they restart from panic just about right away.

I have tried Ubuntu 16.04. 18.04, virtualBox MV and vmWare and even AMD and Intel. 4-6 processors and 4-8GB RAM. The result is always the same.

Other docker containers run happily.

$ docker version
Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:47 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.3
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       774a1f4
  Built:            Thu Feb 28 05:59:55 2019
  OS/Arch:          linux/amd64
  Experimental:     false

$ docker-compose version
docker-compose version 1.17.1, build unknown
docker-py version: 2.5.1
CPython version: 2.7.15rc1
OpenSSL version: OpenSSL 1.1.0g  2 Nov 2017

Here's an image in case it helps.

Here's a representative docker log of a container:

tezos@rob-VirtualBox:~$ docker logs alphanet_node_1
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...
Illegal instruction (core dumped)
Current public chain: 2018-11-30T15:30:56Z-alphanet.
Local chain data: 2018-11-30T15:30:56Z-alphanet.
Configuring the node...

I'd be very thankful for any thoughts or suggestions.

2 risposta

voti

- 0
- 2019-03-06
Ricordo di aver riscontrato lo stessoproblemain alphanetmesifa.Credo si sia scoperto che l'immagine dockerera stata compilatain unmodo chenonfunzionava su alcune configurazioni hardware.Non sono statoin grado ditrovareproblemi/commit di Gitlabesattamenteperilproblema,ma https://gitlab.com/tezos/tezos/issues/220 è correlato.

I recall encountering the same problem in alphanet months ago. I believe it turned out that the docker image had been compiled in a way that failed on some hardware configurations. I have not been able to find gitlab issues/commits for exactly the problem, but https://gitlab.com/tezos/tezos/issues/220 is related.

asbjornenge · Accepted Answer · 2019-03-05

4

2019-03-05

Credo che ciò sia dovuto a unproblema di compilazione con alcunimoduli OCaml che controlla l'architettura hardwarein fase di compilazione Questotrapelanelleimmagini Docker chegenera Illegal instruction quando siesegue un arco diverso.

Puoi leggere ulterioriinformazioni al riguardo qui e qui .

La soluzione è creare da soli l'immagine Docker di Tezos sull'infra/hardware che si desideraeseguirlo. Puoitrovare un Dockerfilefunzionante qui .

<⇨UPDATE

Aggiunti alcuni link dichiarativi di Dockerfile qui
Dockerfile-ubuntu è quello chefaperte,assicurati anche di costruire sull'hardware che devieseguire. Dovrebbefunzionare come leimmagini ufficiali (usandoentrypoint.shecc.)

Iproblemi collegati sembranoessereesattamente ciò che sto vivendo.Grazieper quello!Ho creato Tezos dal Dockerfilee ho acceso un contenitore dall'immagine.Ora stafacendo la stessa cosa: core dump.Sono ancoraperplesso.

The linked issues seem to be exactly what I'm experiencing. Thanks for that! I built Tezos from the Dockerfile and fired up a container from the image. Now it's doing the same thing - core dump. I'm still puzzled.
- 0
- 2019-03-05
- Rob Hitchens
Strano!Questomi ha risolto. Hai "dockerbuild" sulla stessamacchinain cui stai cercando di "docker run"?

Strange! That solved it for me Did you `docker build` on the same machine where you are trying to `docker run` ?
- 0
- 2019-03-05
- asbjornenge
Grazie,sì l'hofatto.Proverò la risposta aggiornata.

Thanks, yes I did. I'll give the updated answer a try.
- 0
- 2019-03-05
- Rob Hitchens
@ RobHitchensfammi sapere se quelfilebasato su Ubuntu ha aiutato,e possometterneinsieme uno corretto con unapartefinale chefunzionerà comegli altri

@RobHitchens let me know if that ubuntu based file helped, and I can put together a proper one with a final part that will work same as the others
- 1
- 2019-03-05
- asbjornenge
Nel casoin cuiti saltifuori qualcosa,hofatto `dockerbuild .`,quindi` docker run -t -ttezos/tezos: alphanettezos-node`.Ora sto lavorando alnuovo suggerimento.

In case something jumps out at you, I did `docker build .`, then `docker run -t -t tezos/tezos:alphanet tezos-node`. Working on the new suggestion now.
- 0
- 2019-03-05
- Rob Hitchens
Ah,stai ancoraeseguendo la vecchiaimmaginetezos dall'hub quindi devifare: `dockerbuild -t rob/tezos: alphanet .`e poi` docker run -rm -it rob/tezos: alphanet` Ilnome dell'immagine `rob/tezos: alpanet`puòessere qualsiasi cosanelformato `proprietario/immagine: versione`

Ah, you are still running the old tezos image from hub then You need to do: `docker build -t rob/tezos:alphanet .` and then `docker run -rm -it rob/tezos:alphanet` The image name `rob/tezos:alpanet` can be anything in the format `owner/image:version`
- 0
- 2019-03-05
- asbjornenge
Chefunzioni.Il Dockerfilenellatua risposta aggiornata (alpino?) Ha creato un contenitore che sembra stabile.È questo l'indizio che stiamo cercando?:-)

That works. The Dockerfile in your updated answer (alpine?) has made a container that seems stable. Is that the clue we're looking for? :-)
- 0
- 2019-03-06
- Rob Hitchens
Cerchiamo di [continuare questa discussionein chat] (https://chat.stackexchange.com/rooms/90649/discussion-between-rob-hitchens-and-asbjornenge).

Let us [continue this discussion in chat](https://chat.stackexchange.com/rooms/90649/discussion-between-rob-hitchens-and-asbjornenge).
- 0
- 2019-03-06
- Rob Hitchens