From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Minikube broken because libvirtd has unconventional socket names
Date: Thu, 09 Jan 2020 10:47:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18133@inbox.vuxu.org> (raw)
[-- 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.
next reply other threads:[~2020-01-09 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 9:47 voidlinux-github [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18133@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).