Recipientes de Docker Reiniciar (132), Instrução Ilegal (Core Dumped)

Question

Recipientes de Docker Reiniciar (132), Instrução Ilegal (Core Dumped)

3

879 2019-03-05

Estou correndo consistentementeem uma show-stopper com Alphanete Dockerno Ubuntu. Eu suspeito que é algo que consistentementeignorei ao configurar. Meus recipientes deencaixefuncionam apenaspor um segundo ou doise depois reiniciar (132).

Alguns cutucandome leva a acreditar queeles reiniciam dopânicoimediatamente.

Eutentei Ubuntu 16.04. 18.04,VirtualBox MVe VMwaree até AMDe Intel. 4-6processadorese 4-8 GB de RAM. O resultado é sempre omesmo.

Outros recipientes deencaixe correm alegremente.

 $ 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

Aquiestá umaimagem caso ajude.

Aquiestá um registro de Docker representativo de um contêiner:

 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...

Euficariamuitogratopor qualquerpensamento ou sugestões.

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 respostas

votos

- 0
- 2019-03-06
Lembro-me deencontrar omesmoproblemaem Alphaanetmeses atrás.Acredito que aimagem do Dockerfoi compilada de umaforma quefalhouem algumas configurações de hardware.Eunão conseguiencontrarproblemas degitlab/commitsparaexatamente oproblema,mas https://gitlab.com/Tezos/Tezos/Problemas/220 está relacionado.

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

Eu acredito queisso épor causa de umproblema de compilação com algummódulo Ocaml que verifica a arquitetura de hardwarenotempo de compilaçãoem vazamentospara asimagens do Docker que lança instruçãoilegal quandoexecutar um arco diferente.

Vocêpode lermais sobreisso aqui e Aqui .

A solução é construir aimagem de Docker Tezosno Infra/Hardware que você desejaexecutá-lo. Vocêpodeencontrar um DockerFile detrabalho aqui .

update

Adicionado alguns DockerFile declarativo aqui
O DockerFile-Ubuntu é o únicopara você,também certifique-se de criar o hardware que vocêprecisa serexecutado. Devefuncionar omesmo que asimagens oficiais (usando EntryPoint.shetc.)

As questões ligadasparecem serexatamente o queestouexperimentando.Obrigadoporisso!Eu construí Tezos do Dockerfilee demiti um recipiente daimagem.Agoraestáfazendo amesma coisa - dump.Eu aindaestouintrigado.

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
Estranho!Isso resolveuparamim vocêfoi construído de docker "namesmamáquina onde vocêestátentando" correr de docker "?

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
Obrigado,simeufiz.Vou dar a resposta atualizada.

Thanks, yes I did. I'll give the updated answer a try.
- 0
- 2019-03-05
- Rob Hitchens
@RobHitchens deixe-me saber seesse arquivobaseadono Ubuntu ajudou,e eupossomontar um apropriado com umapartefinal quefuncionarámesmo que os outros

@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
Caso algopuleem você,eufaço a criação de Docker .`,então 'Docker correr -t -ttezos/tezos: alfanettezos-nó`.Trabalhandonanova sugestão agora.

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,você aindaestáexecutando a antigaimagem de Tezos do Hub,então vocêprecisafazer: `Construir Docker -t Rob/Tezos: Alphanet. E,em seguida,'Docker Run -rm - Rob/Tezos: Alphanet' Rob/Tezos: Alpanet`pode ser qualquer coisanoformato `proprietário/imagem: versão`

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
Issofunciona.O Dockerfileem sua resposta atualizada (Alpine?) Fez um contêiner quepareceestável.Isso é apista queestamosprocurando?:-)

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
Vamos [continuaresta discussãono 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