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

Prometheus causes panic when re-starting stopped VM #102

Closed
twelho opened this issue Jul 6, 2019 · 1 comment
Closed

Prometheus causes panic when re-starting stopped VM #102

twelho opened this issue Jul 6, 2019 · 1 comment
Milestone
v0.4.0

Comments

@twelho
Copy link
Contributor

twelho commented Jul 6, 2019

Tested by calling ignite run -i weaveworks/ignite-ubuntu -> reboot and then trying to start the VM again using ignite start -id <name>. ignite-spawn crashes with the following:

panic: listen unix /var/lib/firecracker/vm/6a2b6ebafcb0e75c/prometheus.sock: bind: address already in use
@twelho twelho added this to the v0.4.0 milestone Jul 6, 2019
twelho added a commit that referenced this issue Jul 6, 2019
@twelho
Import filters, remove loader, use client for all storage interaction
a173283 
This gets rid of the old loading/filtering framework entirely, it's now
replaced by resource clients. The filtering is provided by the filterer,
which can be fed filters from the `filter` package. With this commit,
Ignite builds, `ps`, `start` and `run` are confirmed working, but this
bug persists: #102
@luxas
Copy link
Contributor

luxas commented Jul 9, 2019

Fixed with ef49edd

@luxas luxas closed this as completed Jul 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
2 participants
@luxas @twelho