Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

ignite ps misses vms! #830

Open
lukemarsden opened this issue May 5, 2021 · 3 comments
Open

ignite ps misses vms! #830

lukemarsden opened this issue May 5, 2021 · 3 comments

Comments

@lukemarsden
Copy link

vms are running. ignite ps doesn't notice them! but ignite inspect is able to see them.

compare docker's view of what's running:

$ for X in $(docker ps -aq); do docker inspect $X --format "{{.Config.Labels}}"|grep ignite |cut -d '[' -f 2 |cut -d ']' -f 1|cut -d : -f 2; done
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mrb2aib7q3o2rb3b0
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mr8iaib7q3o2rb3ag
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mr62aib7q3o2rb3a0
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mr3iaib7q3o2rb39g
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mr3iaib7q3o2rb390

to ignite ps's view:

$ sudo ignite ps -t "{{.ObjectMeta.Name}}"
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mr62aib7q3o2rb3a0
tfastpool-37bf0957cf250b8c8a3d5e5c6698b1d80d2e7b8df1ae8ba1d57d8cecf44b895d-vm-c28mrb2aib7q3o2rb3b0
@lukemarsden
Copy link
Author

$ ignite version
Ignite version: version.Info{Major:"0", Minor:"8", GitVersion:"v0.8.0", GitCommit:"77f6859fa4f059f7338738e14cf66f5b9ec9b21c", GitTreeState:"clean", BuildDate:"2020-11-09T20:50:50Z", GoVersion:"go1.14.2", Compiler:"gc", Platform:"linux/amd64", SandboxImage:version.Image{Name:"weaveworks/ignite", Tag:"v0.8.0", Delimeter:":"}, KernelImage:version.Image{Name:"weaveworks/ignite-kernel", Tag:"4.19.125", Delimeter:":"}}
Firecracker version: v0.21.1

@darkowlzz
Copy link
Contributor

@lukemarsden hi, in ignite v0.9.0, we added some improvements to help with this in #787 and #808 .
Can you try ignite v0.9.0 and run ps with -a and check if this is still an issue?
And also, to improve the warning in the output to be more helpful any feedback would be of great help.

@MikePadge
Copy link

Just noting "ps -a" from Dockerland expected behavior is to see images that exist but aren't running. This really confused me when I noticed that that ps vs ps -a was giving me hidden machines that were in fact in a running state.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants