* [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations....
@ 2024-06-26 15:25 acidvegas
2024-06-26 15:31 ` ahesford
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: acidvegas @ 2024-06-26 15:25 UTC (permalink / raw)
To: ml
[-- 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
@ 2024-06-26 15:31 ` ahesford
2024-06-26 16:51 ` acidvegas
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: ahesford @ 2024-06-26 15:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/51015#issuecomment-2192004296
Comment:
Try changing `CGROUP_MODE` to `unified` in `/etc/rc.conf`, reboot, and see if the problem goes away without the extra mount.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
2024-06-26 15:31 ` ahesford
@ 2024-06-26 16:51 ` acidvegas
2024-06-26 16:52 ` acidvegas
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: acidvegas @ 2024-06-26 16:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
New comment by acidvegas on void-packages repository
https://github.com/void-linux/void-packages/issues/51015#issuecomment-2192195837
Comment:
> Try changing `CGROUP_MODE` to `unified` in `/etc/rc.conf`, reboot, and see if the problem goes away without the extra mount.
no dice.
```
[brandon@paloaltonetworks ~]$ incus start elasticsearch-container
Error: Error occurred when starting proxy device: Error: No such file or directory - Failed to safely open namespace file descriptor based on pidfd 3
```
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
2024-06-26 15:31 ` ahesford
2024-06-26 16:51 ` acidvegas
@ 2024-06-26 16:52 ` acidvegas
2024-06-29 13:00 ` dkwo
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: acidvegas @ 2024-06-26 16:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
New comment by acidvegas on void-packages repository
https://github.com/void-linux/void-packages/issues/51015#issuecomment-2192195837
Comment:
> Try changing `CGROUP_MODE` to `unified` in `/etc/rc.conf`, reboot, and see if the problem goes away without the extra mount.
no dice.
```
[brandon@paloaltonetworks ~]$ incus start elasticsearch-container
Error: Error occurred when starting proxy device: Error: No such file or directory - Failed to safely open namespace file descriptor based on pidfd 3
```
Same error as I was getting in the issue I linked.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
` (2 preceding siblings ...)
2024-06-26 16:52 ` acidvegas
@ 2024-06-29 13:00 ` dkwo
2024-06-29 13:02 ` classabbyamp
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: dkwo @ 2024-06-29 13:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/51015#issuecomment-2198153949
Comment:
How exactly can I reproduce this?
With `unified` setup, I can run e.g. Ubuntu containers (without the mkdir/mount thing that was also in lxd runit service)
```
$ incus launch images:ubuntu/24.04 u1t
Launching u1t
$ incus list
+------+---------+--------------------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------+---------+--------------------+------+-----------+-----------+
| u1t | RUNNING | 10.60.1.240 (eth0) | | CONTAINER | 0 |
+------+---------+--------------------+------+-----------+-----------+
```
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
` (3 preceding siblings ...)
2024-06-29 13:00 ` dkwo
@ 2024-06-29 13:02 ` classabbyamp
2024-08-27 18:26 ` rekh127
2024-10-28 6:59 ` [ISSUE] [CLOSED] " acidvegas
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2024-06-29 13:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/51015#issuecomment-2198158650
Comment:
if i had to guess this cgroup mount is done by elogind
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
` (4 preceding siblings ...)
2024-06-29 13:02 ` classabbyamp
@ 2024-08-27 18:26 ` rekh127
2024-10-28 6:59 ` [ISSUE] [CLOSED] " acidvegas
6 siblings, 0 replies; 8+ messages in thread
From: rekh127 @ 2024-08-27 18:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
New comment by rekh127 on void-packages repository
https://github.com/void-linux/void-packages/issues/51015#issuecomment-2313238416
Comment:
I'm also not seeing this with unified and no /sys/fs/cgroup/systemd maybe it's fixed in later versions of incus?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ISSUE] [CLOSED] Incus fails to allow forwarded ports on Void due to systemd expectations....
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
` (5 preceding siblings ...)
2024-08-27 18:26 ` rekh127
@ 2024-10-28 6:59 ` acidvegas
6 siblings, 0 replies; 8+ messages in thread
From: acidvegas @ 2024-10-28 6:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Closed 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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2024-10-28 6:59 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-26 15:25 [ISSUE] Incus fails to allow forwarded ports on Void due to systemd expectations acidvegas
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
2024-08-27 18:26 ` rekh127
2024-10-28 6:59 ` [ISSUE] [CLOSED] " acidvegas
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).