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

docker-compose error when starting validator using sedge-cli #280

Open
mtr980 opened this issue Apr 18, 2023 · 11 comments
Open

docker-compose error when starting validator using sedge-cli #280

mtr980 opened this issue Apr 18, 2023 · 11 comments

Comments

@mtr980
Copy link

mtr980 commented Apr 18, 2023

Describe the bug

  • Using a Macbook M1 chip, installed Docker's latest version and used Sedge V0.5.0. - this step is successful see below

Screen Shot 2023-04-19 at 1 50 35 AM

  • Second step asks for Run the script with the selected services execution, consensus: Y, at this step it shows following error and exit the process.

Screen Shot 2023-04-19 at 1 45 24 AM

tried again using following
sedge cli --network gnosis -c lighthouse -e nethermind

and got the following error
Screen Shot 2023-04-19 at 1 56 05 AM

@cbermudez97
Copy link
Contributor

cbermudez97 commented Apr 18, 2023

Hi @mtr980 and thanks for reporting. Did you install the docker compose plugin? That dependency is required for Sedge. In any case, will recommend you to update Sedge to the lastest version and trying the whole proccess again. You can even try installing dependencies using Sedge sedge deps command.

Edit: docker compose plugin it is not the same as installing docker-compose binary. Try using instead docker compose version to test it.

@mtr980
Copy link
Author

mtr980 commented Apr 18, 2023

docker compose version

Hi @cbermudez97 when I use the latest sedge version, it gives another error related to client API version 1.42 is too new. that's why had to downgrade.
Error with latest version
Screen Shot 2023-04-19 at 2 32 40 AM

In regards to docker compose version shows version 2.17.2 as shown in the screenshot 2 above.

@cbermudez97
Copy link
Contributor

Right, the latest version can sometimes give that error. You can fix it with this command export DOCKER_API_VERSION=1.41.

@cbermudez97
Copy link
Contributor

Also, if Sedge command continues to give an error when running docker-compose commands copy it and run it separately. Share the logs here. That may have some more information about the issue.

@mtr980
Copy link
Author

mtr980 commented Apr 18, 2023

Also, if Sedge command continues to give an error when running docker-compose commands copy it and run it separately. Share the logs here. That may have some more information about the issue.

@cbermudez97 , able to move ahead but getting another error when importing validators.
Screen Shot 2023-04-19 at 2 48 35 AM

@mtr980
Copy link
Author

mtr980 commented Apr 18, 2023

Gone past the above error using export DOCKER_DEFAULT_PLATFORM=linux/amd64, however sync is not working, when
checking log for consensus-client
Screen Shot 2023-04-19 at 3 11 33 AM

and execution-client exited the process with this error
Screen Shot 2023-04-19 at 3 11 41 AM

@stdevMac
Copy link
Member

I'm using Docker version 20.10.23 and it works well with Sedge v1.1.0. Is it possible to update Docker desktop and try the newest version of Sedge? It contains several updates, including an updated version of the clients. Should be easier for us to help you with the latest version.

@mtr980
Copy link
Author

mtr980 commented Apr 19, 2023

I'm using Docker version 20.10.23 and it works well with Sedge v1.1.0. Is it possible to update Docker desktop and try the newest version of Sedge? It contains several updates, including an updated version of the clients. Should be easier for us to help you with the latest version.

Hi @stdevMac all up to date, yet got stuck with these errors.
Screen Shot 2023-04-19 at 4 00 55 AM

@stdevMac
Copy link
Member

Did you follow the instructions here to install docker on Mac?

@stdevMac
Copy link
Member

Some useful links: docker/for-mac#5283 (comment)

@stdevMac
Copy link
Member

I think once you solve the docker error you should be able to run Sedge without issues, Let us know how it goes, please!

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

3 participants