-
Notifications
You must be signed in to change notification settings - Fork 594
Open
Labels
Description
data-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.
serchuz, jackyxuebin, anikrajc, tf42src and wt911122
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
tf42src commentedon Jan 14, 2019
Same here.
18566246732 commentedon Jun 19, 2019
same here, any solutions ?
bvans commentedon Jul 16, 2019
Same here
JackyChou commentedon Aug 13, 2019
I have encountered this problem when I get start with docker.
https://docs.docker.com/get-started/part5/
And I found the container in myvm2 is Preparing.
$docker stack ps getstartedlab
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
7uiy2jfca5v9 getstartedlab_web.1 pythonmonk/get-started:part2 myvm2 Running Preparing 48 seconds ago
33zbxjp55ski getstartedlab_web.2 pythonmonk/get-started:part2 myvm1 Running Running 46 seconds ago
mt59tf8oywnc getstartedlab_web.3 pythonmonk/get-started:part2 myvm1 Running Running 46 seconds ago
weha4ugjk3cw getstartedlab_web.4 pythonmonk/get-started:part2 myvm2 Running Preparing 48 seconds ago
524ifqhefxgl getstartedlab_web.5 pythonmonk/get-started:part2 myvm1 Running Running 46 seconds ago
This maybe the reason for this problem.
$docker-machine ssh myvm2 "docker container ls"
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
jnovack commentedon Sep 5, 2019
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: #106)
I suggest you either download, apply the pull request yourself, and rebuild yourself, or move-on to another project.