Github messages for voidlinux
 help / color / mirror / Atom feed
From: acidvegas <acidvegas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations....
Date: Wed, 26 Jun 2024 17:25:12 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51015@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

New issue by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/issues/51015

Description:
### Is this a new report?

Yes

### System Info

Void

### Package(s) Affected

incus

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/lxc/incus/issues/625

tldr; the solution is to run:
```
mkdir /sys/fs/cgroup/systemd
mount -t cgroup -o none,name=systemd systemd /sys/fs/cgroup/systemd 
```

and then you can start your containers......I guess incus on void is expecting systemd mounts in the cgroup

Classic case of devs only making things catered to ubuntu/debian builds

Reporting this here, doubt anyone is going to fix it.

Cheers

### Expected behaviour

Containers running

### Actual behaviour

Containers wont run and bind to forwarded ports.

### Steps to reproduce

read the linked issue

             reply	other threads:[~2024-06-26 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 15:25 acidvegas [this message]
2024-06-26 15:31 ` ahesford
2024-06-26 16:51 ` acidvegas
2024-06-26 16:52 ` acidvegas
2024-06-29 13:00 ` dkwo
2024-06-29 13:02 ` classabbyamp

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-51015@inbox.vuxu.org \
    --to=acidvegas@users.noreply.github.com \
    --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).