* [ISSUE] Minikube broken because libvirtd has unconventional socket names
@ 2020-01-09 9:47 voidlinux-github
2020-01-09 23:02 ` Minikube broken because libvirtd has unconventional socket names (temporary fix included) voidlinux-github
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: voidlinux-github @ 2020-01-09 9:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
New issue by leonardlorenz on void-packages repository
https://github.com/void-linux/void-packages/issues/18133
Description:
### System
Thinkpad T430s with intel i5 3320m with 8gb ram.
* xuname:
Void 5.3.18_1 x86_64 GenuineIntel notuptodate rFFF
* package:
- minikube
- libvirt
### Expected behavior
libvirt creates /var/run/libvirt/libvirtd-sock
minikube can find libvirtd-sock and starts up fine
### Actual behavior
libvirt creates /var/run/libvirt/libvirt-sock
minikube can't find libvirtd-sock because it is not named by convention
### Steps to reproduce the behavior
xbps-install -S libvirt
sudo ln -s /etc/sv/libvirtd /var/service
sudo ln -s /etc/sv/virtlogd /var/service
minikube start
### Notes
I have temporarily fixed the problem by symlinking the socket to the expected location.
I will look into fixing the package template later today but I can't promise anything.
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Minikube broken because libvirtd has unconventional socket names (temporary fix included) 2020-01-09 9:47 [ISSUE] Minikube broken because libvirtd has unconventional socket names voidlinux-github @ 2020-01-09 23:02 ` voidlinux-github 2020-01-10 9:31 ` voidlinux-github 2020-02-25 10:01 ` [ISSUE] [CLOSED] " leonardlorenz 2 siblings, 0 replies; 4+ messages in thread From: voidlinux-github @ 2020-01-09 23:02 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 369 bytes --] New comment by leonardlorenz on void-packages repository https://github.com/void-linux/void-packages/issues/18133#issuecomment-572796703 Comment: I really don't see another solution outside of symlinking libvirt-sock to libvirt-sockd in the post_install() function of libvirt's template. Someone more versed with libvirt and packaging should take a look if possible. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Minikube broken because libvirtd has unconventional socket names (temporary fix included) 2020-01-09 9:47 [ISSUE] Minikube broken because libvirtd has unconventional socket names voidlinux-github 2020-01-09 23:02 ` Minikube broken because libvirtd has unconventional socket names (temporary fix included) voidlinux-github @ 2020-01-10 9:31 ` voidlinux-github 2020-02-25 10:01 ` [ISSUE] [CLOSED] " leonardlorenz 2 siblings, 0 replies; 4+ messages in thread From: voidlinux-github @ 2020-01-10 9:31 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 461 bytes --] New comment by leonardlorenz on void-packages repository https://github.com/void-linux/void-packages/issues/18133#issuecomment-572796703 Comment: I really don't see another solution outside of symlinking libvirt-sock to libvirt-sockd in the post_install() function of libvirt's template. Someone more versed with libvirt and packaging should take a look if possible. Edit: nevermind the above wouldn't work either, since the symlink gets purged on reboot. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ISSUE] [CLOSED] Minikube broken because libvirtd has unconventional socket names (temporary fix included) 2020-01-09 9:47 [ISSUE] Minikube broken because libvirtd has unconventional socket names voidlinux-github 2020-01-09 23:02 ` Minikube broken because libvirtd has unconventional socket names (temporary fix included) voidlinux-github 2020-01-10 9:31 ` voidlinux-github @ 2020-02-25 10:01 ` leonardlorenz 2 siblings, 0 replies; 4+ messages in thread From: leonardlorenz @ 2020-02-25 10:01 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 932 bytes --] Closed issue by leonardlorenz on void-packages repository https://github.com/void-linux/void-packages/issues/18133 Description: ### System Thinkpad T430s with intel i5 3320m with 8gb ram. * xuname: - Void 5.3.18_1 x86_64 GenuineIntel notuptodate rFFF * package: - minikube - libvirt ### Expected behavior libvirt creates /var/run/libvirt/libvirtd-sock minikube can find libvirtd-sock and starts up fine ### Actual behavior libvirt creates /var/run/libvirt/libvirt-sock minikube can't find libvirtd-sock because it is not named by convention ### Steps to reproduce the behavior xbps-install -S libvirt sudo ln -s /etc/sv/libvirtd /var/service sudo ln -s /etc/sv/virtlogd /var/service minikube start ### Notes I have temporarily fixed the problem by symlinking the socket to the expected location. I will look into fixing the package template later today but I can't promise anything. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-02-25 10:01 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-01-09 9:47 [ISSUE] Minikube broken because libvirtd has unconventional socket names voidlinux-github 2020-01-09 23:02 ` Minikube broken because libvirtd has unconventional socket names (temporary fix included) voidlinux-github 2020-01-10 9:31 ` voidlinux-github 2020-02-25 10:01 ` [ISSUE] [CLOSED] " leonardlorenz
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).