-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Can't add network in docker container #224
Comments
OK, I figured out why. There's nothing wrong with the code, but my configurations.
|
Hey @shawnwang0715, thank you very much for this information ❤️. I will make sure to fix these two issues from points 1 and 3. For point 2, this is not an issue. Synpress uses kovan by default, so if you don't pass these env vars to docker image, it will obviously use default network which is kovan. I will make sure to fix this in upcoming synpress release (ETA next week). btw. sorry for not looking in to it earlier. I'm currently a little bit busy with other stuff. Cheers, |
Hey @drptbl, I'm not sure whether this is an issue, but when I tried to enter the wrong values (for example, a Maybe displaying error messages in the console would help other devs when they using docker. How do you think? Regards, |
@shawnwang0715 Yeah, for sure. Synpress error handling has to be improved and be more descriptive to avoid long debugging process. |
Hey @shawnwang0715, I've addressed all issues you've described above. Sorry for delay! You can check it out using Thanks for awesome feedback 🙏. All Best, |
Sorry, I can't find a way to re-open the issue in #215, so I create a new one.
When I try to add a network in docker container, it always gets stuck in here:
synpress/commands/metamask.js
Lines 228 to 230 in b9c2f3f
Here's my
docker-compose.yml
:After starting the docker container, I run these commands:
My synpress.json has nothing special. I only changed the
baseUrl
Then I always get
Could you check whether adding network works in docker? Thanks!
The text was updated successfully, but these errors were encountered: