Skip to content
This repository has been archived by the owner on Jul 14, 2022. It is now read-only.

[BUG] docker error at running genesis-csv-to-json #45

Closed
marco-sundsk opened this issue Nov 20, 2019 · 2 comments
Closed

[BUG] docker error at running genesis-csv-to-json #45

marco-sundsk opened this issue Nov 20, 2019 · 2 comments
Assignees
Labels
E1 Stake wars effort 1 easy S3 Stake Wars Severity 3

Comments

@marco-sundsk
Copy link

Describe the bug or test
When exec start_stakewars.py, it shows error:
error: Found argument '--tracked-shards' which wasn't expected, or isn't valid in this context

Here is the detail info
root@buildlinks-test-platform:~/near_stakewars/nearcore# docker logs -f 383714fe3e5d
Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
Running /etc/my_init.d/10_syslog-ng.init...
Nov 20 13:22:04 383714fe3e5d syslog-ng[13]: syslog-ng starting up; version='3.13.2'
Booting runit daemon...
Runit started as PID 21
Running genesis-csv-to-json --home=/srv/genesis-csv-to-json --chain-id=stakewars --tracked-shards=...
error: Found argument '--tracked-shards' which wasn't expected, or isn't valid in this context
USAGE:
genesis-csv-to-json --chain-id --home
For more information try --help
genesis-csv-to-json exited with status 1.
Shutting down runit daemon (PID 21)...

How to Reproduce
Steps to reproduce the behavior:

  1. clean .near
  2. ./scripts/start_stakewars.py --init --signer-keys --account-id=<your_account_id>
  3. downlaod and move accounts.csv into ~/.near folder
  4. Run scripts/start_stakewars.py

Expected behavior OR Outcome of test
start node successfully.

Specs (please complete the following information):

  • OS: Ubuntu 18.04
  • Which cloud / on-premise: AliYun
  • CPU: Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
  • RAM: 4G
  • Disk space: 500G SSD

Additional context
docker image info is here:
root@buildlinks-test-platform:~/near_stakewars/nearcore/scripts# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
nearprotocol/nearcore stakewars 040fdad633e6 42 hours ago 234MB
nearprotocol/nearcore latest 4b24bba194ad 2 days ago 234MB
v2tec/watchtower latest 3069a9fb302a 20 months ago 9.49MB

Screenshots Optional
If applicable, add screenshots to help explain your problem.
bug1

@marco-sundsk marco-sundsk added the totriage this issue needs ENG triage label Nov 20, 2019
@ailisp
Copy link
Contributor

ailisp commented Nov 21, 2019

@bowenwang1996 Do you aware of this old version and the fix? The stakewar tag is override by newer one, and in the newer stakewars this issue is fixed, as in:

nearprotocol/nearcore         stakewars           f805b2a1ae69        21 hours ago        128MB

@ailisp ailisp added E3 Stake wars effort 3 easy S3 Stake Wars Severity 3 and removed totriage this issue needs ENG triage labels Nov 21, 2019
@ailisp ailisp closed this as completed Nov 21, 2019
@bowenwang1996
Copy link
Contributor

Yes it is probably incompatible docker images.

@ailisp ailisp added E1 Stake wars effort 1 and removed E3 Stake wars effort 3 labels Nov 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E1 Stake wars effort 1 easy S3 Stake Wars Severity 3
Projects
None yet
Development

No branches or pull requests

3 participants