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

Error when running on Fedora 30 #72

Open
corollari opened this issue Jun 24, 2019 · 0 comments
Open

Error when running on Fedora 30 #72

corollari opened this issue Jun 24, 2019 · 0 comments

Comments

@corollari
Copy link

Description

neo-python can't connect to the container running neo-privatenet-docker, producing the following error:

[E 190624 10:16:25 prompt:273] Error: private network container doesn't seem to be running, or RPC is not enabled.

Reproduction steps

Follow the steps outlined in https://hub.docker.com/r/cityofzion/neo-python/ on Fedora 30, running the following:

# Pull the latest images from Docker hub
docker pull cityofzion/neo-python
docker pull cityofzion/neo-privatenet

# Start the private network container. Maps the current working directory on the host into 
# `/neo-python/sc/` and exposes the ports.
docker run --rm -d --name neo-privatenet -p 20333-20336:20333-20336/tcp -p 30333-30336:30333-30336/tcp cityofzion/neo-privatenet

# Start the neo-python container
docker run --rm -it --net=host -v $(pwd):/neo-python/sc -h neo-python --name neo-python cityofzion/neo-python /bin/bash

# Start neo-python
np-prompt -p -v

Details

Full shell output

Line breaks added to increase readability

[corollari@localhost neo-priv]$ docker pull cityofzion/neo-python
Using default tag: latest
latest: Pulling from cityofzion/neo-python
Digest: sha256:b4a8a830e64b761c5c54c6d96bcc5251ff9795d2106e5a78f001ac06b1a70fdc
Status: Image is up to date for cityofzion/neo-python:latest

[corollari@localhost neo-priv]$ docker pull cityofzion/neo-privatenet
Using default tag: latest
latest: Pulling from cityofzion/neo-privatenet
Digest: sha256:3d1ae4149dc68e9a9155d0c8081d55bf49e7fa614e275d137850ff1b7f0073f7
Status: Image is up to date for cityofzion/neo-privatenet:latest

[corollari@localhost neo-priv]$ docker run --rm -d --name neo-privatenet -p 20333-20336:20333-20336/tcp -p 30333-30336:30333-30336/tcp cityofzion/neo-privatenet
0b92e13483bd6c69ae343fe3e0ca2e3cf6f69d67ff42e5b796b76c58978df924

[corollari@localhost neo-priv]$ docker run --rm -it --net=host -v $(pwd):/neo-python/sc -h neo-python --name neo-python cityofzion/neo-python /bin/bash

root@neo-python:/neo-python# np-prompt -p -v
[E 190624 10:16:25 prompt:273] Error: private network container doesn't seem to be running, or RPC is not enabled.

root@neo-python:/neo-python#

docker-ps output

CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS                                                                        NAMES
46e3ab0b351a        cityofzion/neo-python       "/bin/bash"              16 minutes ago      Up 16 minutes                                                                                    neo-python
0b92e13483bd        cityofzion/neo-privatenet   "/bin/bash /opt/run_…"   17 minutes ago      Up 17 minutes       0.0.0.0:20333-20336->20333-20336/tcp, 0.0.0.0:30333-30336->30333-30336/tcp   neo-privatenet

Versions

Docker: version 18.06.3, build d7080c1
OS: Fedora 30 (linux kernel 4.20.16-200.fc29.x86_64)

Notes

I came across this problem when debugging a downstream issue (see CityOfZion/neo-local#178) that I think is directly caused by this error.

The problem I'm seeing could also be caused by something in neo-python, but based on my testing I think the root cause is in neo-privatenet-docker. Still, I could be wrong, so if you think the issue is caused by something else just tell me and I'll transfer the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant