8000 Error scaffolding a chain with Docker · Issue #1202 · ignite/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Error scaffolding a chain with Docker #1202

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

Closed
fadeev opened this issue May 27, 2021 · 8 comments
Closed

Error scaffolding a chain with Docker #1202

fadeev opened this issue May 27, 2021 · 8 comments
Labels

Comments

@fadeev
Copy link
Contributor
fadeev commented May 27, 2021

Describe the bug
Doesn't scaffold a chain with Docker. (from Discord)

To Reproduce

docker run -ti \
    -w /app \
    -v `pwd`/home:/home/tendermint \
    -v `pwd`/app:/app \
    starport/cli:0.16.0 app github.com/hello/planet

Output:

chdir /app/planet: no such file or directory

Please provide output of commands

  • starport version
  • go version
  • uname -a
@fadeev fadeev added the report label May 27, 2021
@ilgooz
Copy link
Member
ilgooz commented May 27, 2021

This commamd looks incorrect in two ways.

Both -v flags are using the same dir on the host machine (pwd), they should use different dirs.

-v $PWD/app:/app actually should be -v $PWD:/app

@fadeev
Copy link
Contributor Author
fadeev commented May 27, 2021

@ilgooz ok, thanks! I'll ask them to use the exact command from the docs and see if it works. The thing is, the command above didn't work for them, but it worked fine on my machine.

@martin-sweeny
Copy link
Contributor

This commamd looks incorrect in two ways.

Both -v flags are using the same dir on the host machine (pwd), they should use different dirs.

-v $PWD/app:/app actually should be -v $PWD:/app

The -v flags are using different dirs, but relative to the current dir. I don't want to pollute my home directory with artifacts from this.

@martin-sweeny
Copy link
Contributor
martin-sweeny commented May 27, 2021

@fadeev

Please provide output of commands

  • starport version
  • go version
  • uname -a

These have no relevance since I'm using go and starport in docker...

@fadeev
Copy link
Contributor Author
fadeev commented May 30, 2021

Solution was reported by the author:

docker run -ti \
    -w /app \
    -v $PWD/home:/home/tendermint \
    -v $PWD:/app \
    starport/cli:0.16.0 app github.com/hello/planet

chmod 777 -R ./*

docker run -ti \
    -w /app \
    -v $PWD/home:/home/tendermint \
    -v $PWD/planet:/app \
    -p 1317:1317 \
    -p 26657:26657 \
    starport/cli:0.16.0 serve -p /app

cd planet/vue

npm i
npm run serve

To me, this still looks like a permissions issue with nothing we need to fix (perhaps, add this to the docs?). Please, reopen if it's still a problem.

8000 @fadeev fadeev closed this as completed May 30, 2021
@martin-sweeny
Copy link
Contributor
martin-sweeny commented Jun 14, 2021

To me, this still looks like a permissions issue with nothing we need to fix (perhaps, add this to the docs?). Please, reopen if it's still a problem.
@fadeev

It looks to me like a permissions issue stemming from the Dockerfile, though. I've reproduced this on both Artix and Ubuntu, too. If I have time this week I'll try fiddling with the Dockerfile; and, hopefully, submit a PR if I find a fix

@fadeev
Copy link
Contributor Author
fadeev commented Jun 14, 2021

@martin-sweeny oh, that'd be wonderful 🙏 I can't reproduce this, but this might indeed be an issue for other people.

@martin-sweeny
Copy link
Contributor

@fadeev I wrote #1243 to try to address it - seems to work better for me, at least

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

No branches or pull requests

3 participants
0