Unable to display content while containers are preparing
See original GitHub issuedata-provider.js fails during container preparation (downloading
, preparing
).
This causes a complete halt of the visualization in the event you have a restart:always
container failing on preparing
(e.g. ‘Invalid mount type…’, etc)
data-provider.js:85 Uncaught (in promise) TypeError: Cannot read property 'ContainerID' of undefined
at data-provider.js:85
at a (index.js:326)
at Function.<anonymous> (index.js:3241)
at s (data-provider.js:67)
at Array.forEach (<anonymous>)
at w (data-provider.js:221)
at data-provider.js:280
Not sure why, as it should’ve had a container ID to get that far.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:5
Top Results From Across the Web
Can someone help me with the correct containers-prepare ...
I'm getting error when I run the generated containers-prepare-parameter.yaml file. Can someone please help. I don't need ceph storage.
Read more >Not able to access a file created by a docker container from ...
First container is a flask application which does some work on data and creates log file. While the other container is R shiny...
Read more >How to Fix and Debug Docker Containers Like a Superhero
Container errors are tricky to diagnose, but some investigative magic works wonders. Read along to learn how to debug Docker containers.
Read more >How to Debug and Fix Common Docker Issues - DigitalOcean
When you look at a Dockerfile , you can clearly see the ... But you may run into issues making those containers communicate...
Read more >Kubernetes Error Codes: Failed to Pull Image | Datree.io
containers.image` field but consecutive attempts have failed. It's “backing off” by waiting a while before trying again. When you see ` ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The maintainers have made it clear that to keep this project as “simple as possible”, they do not care about outstanding issues or enhancing the project. (Reference: https://github.com/dockersamples/docker-swarm-visualizer/pull/106)
I suggest you either download, apply the pull request yourself, and rebuild yourself, or move-on to another project.
Same here