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

Initial BN log is "no such container" #520

Closed
morrigan opened this issue Mar 2, 2021 · 0 comments · Fixed by #523
Closed

Initial BN log is "no such container" #520

morrigan opened this issue Mar 2, 2021 · 0 comments · Fixed by #523
Assignees
Labels
bug Something isn't working priority: P3 important UX

Comments

@morrigan
Copy link
Member

morrigan commented Mar 2, 2021

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Click to remove all beacon nodes inside app
  2. Add new beacon node
  3. Beacon node is running
  4. Open logs, see error Error: No such container: localhost-beacon-node while container is running with that name

Expected behavior
Probably at some point the BN was trying to be reached while being created however this seems to give a false statement and should be updated or whatsoever.

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

Desktop:

  • OS: Windows 10
  • Network [e.g. Pyrmont]
  • Chain Guardian Version 0.5.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority: P3 important UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants