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

Network fails to start with Podman #257

Closed
crystalin opened this issue Jun 28, 2022 · 6 comments · Fixed by #501
Closed

Network fails to start with Podman #257

crystalin opened this issue Jun 28, 2022 · 6 comments · Fixed by #501
Assignees
Labels
bug Something isn't working

Comments

@crystalin
Copy link
Contributor

I'm testing zombienet with podman (version 3.4.2) and can't run the basic example, I'm not sure how to troubleshoot it:

└--╼ node dist/cli.js -p podman spawn examples/0001-small-network.toml 

         Using provider: podman

         Launching network under namespace: zombie-02cfbcd1
                 Using temporary directory: /tmp/zombie-02cfbcd1_-22926-53EgcilrKiYT

         Monitor: prometheus - url: http://127.0.0.1:36097

         Monitor: tempo - url: http://127.0.0.1:38713

         Monitor: grafana - url: http://127.0.0.1:45381

        launching temp pod with image docker.io/paritypr/polkadot-debug:master
                 with command: bash -c polkadot build-spec --chain rococo-local --disable-default-bootnode > /cfg/rococo-local-plain.json

It is stuck there forever

@crystalin crystalin changed the title Network fails to start Network fails to start with Podman Jun 28, 2022
@pepoviola pepoviola self-assigned this Jul 8, 2022
@pepoviola
Copy link
Collaborator

Hi @crystalin, thanks for reporting :) I just trying with podman 3.0.1 and works as expected. Can you check the logs of the temp pod when is stuck there?

Thanks!

@pepoviola pepoviola added the question Further information is requested label Jul 8, 2022
@crystalin
Copy link
Contributor Author

@pepoviola thank you for looking at it.
I'm really a newbie concerning podman, can you tell me how to properly get the logs so I can paste them here ?

@pepoviola
Copy link
Collaborator

@pepoviola thank you for looking at it. I'm really a newbie concerning podman, can you tell me how to properly get the logs so I can paste them here ?

You can check the logs with this command

podman logs temp_pod-temp

Can you paste the logs here, so I can check why is stuck there 👍

@crystalin
Copy link
Contributor Author

podman logs temp_pod-temp

It returns nothing (I tried when it was running/stuck and also after killing it)

@tobbelobb
Copy link
Contributor

tobbelobb commented Oct 1, 2022

I'm on podman version 3.4.4, Ubuntu 22.04, and I see a similar behavior:

Screenshot from 2022-10-01 18-30-26

The podman logs tell me it's waiting for tar:

Screenshot from 2022-10-01 18-36-44

I forced it to stop waiting by fiddling with make_transfer_container(), and got this error:

$ node dist/cli.js -p podman spawn examples/0001-small-network.toml
...
Error: ENOENT: no such file or directory, copyfile '/tmp/zombie-922c5be6_-328968-rT47IK5tVg9Y/temp/cfg/rococo-local-plain.json' -> '/tmp/zombie-922c5be6_-328968-rT47IK5tVg9Y/rococo-local-plain.json'

I tried again, this time copying the rococo-local-plain.json into the right place manually. It worked for a little longer, but then I got:

$ node dist/cli.js -p podman spawn examples/0001-small-network.toml
...
Error: ENOENT: no such file or directory, copyfile '/tmp/zombie-7e6a3fea_-552529-2Maz0OQx7HSX/temp-collator/cfg/genesis-state' -> '/tmp/zombie-7e6a3fea_-552529-2Maz0OQx7HSX/100/genesis-state'

So the genesis-state file is also missing. I suspect some kind of error with permissions or something.

@pepoviola
Copy link
Collaborator

Thanks @tobbelobb, I will look asap.

@pepoviola pepoviola added bug Something isn't working and removed question Further information is requested labels Oct 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants