#incus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #incus, aggregated by home.social.
-
I have secured my home access a bit more.
I now run a Wireguard VPN-server inside an Incus container.
The container has two interfaces.
One on my LAN and one only shared with the host via Incus.The host runs a ssh-server that only binds to the interface shared with the container.
So the only access to my ssh-server is through the VPN.
The VPN is configured with a PSK to be more resistant against post quantum encryption.
My ssh-server only accepts key-authentication and post quantum KEX.
-
I have secured my home access a bit more.
I now run a Wireguard VPN-server inside an Incus container.
The container has two interfaces.
One on my LAN and one only shared with the host via Incus.The host runs a ssh-server that only binds to the interface shared with the container.
So the only access to my ssh-server is through the VPN.
The VPN is configured with a PSK to be more resistant against post quantum encryption.
My ssh-server only accepts key-authentication and post quantum KEX.
-
I have secured my home access a bit more.
I now run a Wireguard VPN-server inside an Incus container.
The container has two interfaces.
One on my LAN and one only shared with the host via Incus.The host runs a ssh-server that only binds to the interface shared with the container.
So the only access to my ssh-server is through the VPN.
The VPN is configured with a PSK to be more resistant against post quantum encryption.
My ssh-server only accepts key-authentication and post quantum KEX.
-
I have secured my home access a bit more.
I now run a Wireguard VPN-server inside an Incus container.
The container has two interfaces.
One on my LAN and one only shared with the host via Incus.The host runs a ssh-server that only binds to the interface shared with the container.
So the only access to my ssh-server is through the VPN.
The VPN is configured with a PSK to be more resistant against post quantum encryption.
My ssh-server only accepts key-authentication and post quantum KEX.
-
I have secured my home access a bit more.
I now run a Wireguard VPN-server inside an Incus container.
The container has two interfaces.
One on my LAN and one only shared with the host via Incus.The host runs a ssh-server that only binds to the interface shared with the container.
So the only access to my ssh-server is through the VPN.
The VPN is configured with a PSK to be more resistant against post quantum encryption.
My ssh-server only accepts key-authentication and post quantum KEX.
-
@violet
There are many opinions and combinations possible, of course. I prefer simple, community backed, and solid foss blocks that interoperate. That converged to:
* #debian for base OS
* data on encrypted #zfs
* #incus for VM and system containers management (formerly LXD)
* #ansible for automation, with the debops collectionInfrastructure for people, to solve our problems and at our scale, with all the tools under direct control of worker sysadmins
-
@violet
There are many opinions and combinations possible, of course. I prefer simple, community backed, and solid foss blocks that interoperate. That converged to:
* #debian for base OS
* data on encrypted #zfs
* #incus for VM and system containers management (formerly LXD)
* #ansible for automation, with the debops collectionInfrastructure for people, to solve our problems and at our scale, with all the tools under direct control of worker sysadmins
-
@violet
There are many opinions and combinations possible, of course. I prefer simple, community backed, and solid foss blocks that interoperate. That converged to:
* #debian for base OS
* data on encrypted #zfs
* #incus for VM and system containers management (formerly LXD)
* #ansible for automation, with the debops collectionInfrastructure for people, to solve our problems and at our scale, with all the tools under direct control of worker sysadmins
-
@violet
There are many opinions and combinations possible, of course. I prefer simple, community backed, and solid foss blocks that interoperate. That converged to:
* #debian for base OS
* data on encrypted #zfs
* #incus for VM and system containers management (formerly LXD)
* #ansible for automation, with the debops collectionInfrastructure for people, to solve our problems and at our scale, with all the tools under direct control of worker sysadmins
-
@violet
There are many opinions and combinations possible, of course. I prefer simple, community backed, and solid foss blocks that interoperate. That converged to:
* #debian for base OS
* data on encrypted #zfs
* #incus for VM and system containers management (formerly LXD)
* #ansible for automation, with the debops collectionInfrastructure for people, to solve our problems and at our scale, with all the tools under direct control of worker sysadmins
-
@jonny I installed #Forgejo in an #Incus container in about an hour, and by golly, so should you. (Slaps hood of $300 used Dell Optiplex 3060)
#SelfHosting #OpenSource -
@jonny I installed #Forgejo in an #Incus container in about an hour, and by golly, so should you. (Slaps hood of $300 used Dell Optiplex 3060)
#SelfHosting #OpenSource -
@jonny I installed #Forgejo in an #Incus container in about an hour, and by golly, so should you. (Slaps hood of $300 used Dell Optiplex 3060)
#SelfHosting #OpenSource -
@jonny I installed #Forgejo in an #Incus container in about an hour, and by golly, so should you. (Slaps hood of $300 used Dell Optiplex 3060)
#SelfHosting #OpenSource -
@jonny I installed #Forgejo in an #Incus container in about an hour, and by golly, so should you. (Slaps hood of $300 used Dell Optiplex 3060)
#SelfHosting #OpenSource -
Incus 7.0 LTS:rilasciato il gestore di container e macchine virtuali con supporto a lungo termine
Incus è un sistema avanzato per la gestione di container (ambienti isolati che condividono il kernel del sistema operativo ma funzionano come piccoli sistemi indipendenti) e macchine virtuali (sistemi operativi completi eseguiti in modo isolato tramite un hypervisor)#incus #UnoLinux #linux #gnulinuxitalia #gnulinux
-
Incus 7.0 LTS:rilasciato il gestore di container e macchine virtuali con supporto a lungo termine
Incus è un sistema avanzato per la gestione di container (ambienti isolati che condividono il kernel del sistema operativo ma funzionano come piccoli sistemi indipendenti) e macchine virtuali (sistemi operativi completi eseguiti in modo isolato tramite un hypervisor)#incus #UnoLinux #linux #gnulinuxitalia #gnulinux
-
Incus 7.0 LTS:rilasciato il gestore di container e macchine virtuali con supporto a lungo termine
Incus è un sistema avanzato per la gestione di container (ambienti isolati che condividono il kernel del sistema operativo ma funzionano come piccoli sistemi indipendenti) e macchine virtuali (sistemi operativi completi eseguiti in modo isolato tramite un hypervisor)#incus #UnoLinux #linux #gnulinuxitalia #gnulinux
-
Incus 7.0 LTS:rilasciato il gestore di container e macchine virtuali con supporto a lungo termine
Incus è un sistema avanzato per la gestione di container (ambienti isolati che condividono il kernel del sistema operativo ma funzionano come piccoli sistemi indipendenti) e macchine virtuali (sistemi operativi completi eseguiti in modo isolato tramite un hypervisor)#incus #UnoLinux #linux #gnulinuxitalia #gnulinux
-
Incus 7.0 LTS:rilasciato il gestore di container e macchine virtuali con supporto a lungo termine
Incus è un sistema avanzato per la gestione di container (ambienti isolati che condividono il kernel del sistema operativo ma funzionano come piccoli sistemi indipendenti) e macchine virtuali (sistemi operativi completi eseguiti in modo isolato tramite un hypervisor)#incus #UnoLinux #linux #gnulinuxitalia #gnulinux
-
Done! Project deploy a self-hosted Vaultwarden instance complete.
It was easier than I had thought it thought it would be. The only bugs I dealt with came from Incus, and they were easy to solve. And was my first time using docker on a remote server 🥳😂.
After the instance was deployed, I wrote a bash script to backup my data ... used crontab to automate it.
#selfhosted #linux #incus #vaultwarden #password #security #docker #container #bash #crontab #deploy #devops #sysadmin
-
Just saw a post on Lemmy about Vaultwarden ... I am going to set mine now. Updates will be made if it goes well.
-
Incus 7.0 LTS arrives with five years of support, updated requirements, security fixes, OCI image support, and storage improvements.
https://linuxiac.com/incus-7-0-lts-container-and-virtual-machine-manager-released/ -
Incus 7.0 LTS arrives with five years of support, updated requirements, security fixes, OCI image support, and storage improvements.
https://linuxiac.com/incus-7-0-lts-container-and-virtual-machine-manager-released/ -
Incus 7.0 LTS arrives with five years of support, updated requirements, security fixes, OCI image support, and storage improvements.
https://linuxiac.com/incus-7-0-lts-container-and-virtual-machine-manager-released/ -
Incus 7.0 LTS arrives with five years of support, updated requirements, security fixes, OCI image support, and storage improvements.
https://linuxiac.com/incus-7-0-lts-container-and-virtual-machine-manager-released/ -
Incus 7.0 LTS arrives with five years of support, updated requirements, security fixes, OCI image support, and storage improvements.
https://linuxiac.com/incus-7-0-lts-container-and-virtual-machine-manager-released/ -
#Incus 7.0 LTS is now out!
That's already the second Long Term Support release for the Incus project and it should be a great upgrade both for users of Incus 6.23 and those on 6.0.6 LTS!
https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641 -
#Incus 7.0 LTS is now out!
That's already the second Long Term Support release for the Incus project and it should be a great upgrade both for users of Incus 6.23 and those on 6.0.6 LTS!
https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641 -
#Incus 7.0 LTS is now out!
That's already the second Long Term Support release for the Incus project and it should be a great upgrade both for users of Incus 6.23 and those on 6.0.6 LTS!
https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641 -
#Incus 7.0 LTS is now out!
That's already the second Long Term Support release for the Incus project and it should be a great upgrade both for users of Incus 6.23 and those on 6.0.6 LTS!
https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641 -
#Incus 7.0 LTS is now out!
That's already the second Long Term Support release for the Incus project and it should be a great upgrade both for users of Incus 6.23 and those on 6.0.6 LTS!
https://discuss.linuxcontainers.org/t/incus-7-0-lts-has-been-released/26641 -
I used to name my VM's when I launched them, last week I forgot to do it and I have been allowing incus to do the naming now.
-
I used to name my VM's when I launched them, last week I forgot to do it and I have been allowing incus to do the naming now.
-
I used to name my VM's when I launched them, last week I forgot to do it and I have been allowing incus to do the naming now.
-
I used to name my VM's when I launched them, last week I forgot to do it and I have been allowing incus to do the naming now.
-
Pour ceux qui auraient la mauvaise idée de passer trop tôt la mise à jour d'Ubuntu 24.04 à 26.04 sur un serveur avec #incus : attention, les nouvelles sécurités par défaut d' AppArmor cassent tout ! La solution ici : https://discuss.linuxcontainers.org/t/issues-in-ubuntu-26-04-apt-not-working-in-unprivileged-lxcs/26591
-
Pour ceux qui auraient la mauvaise idée de passer trop tôt la mise à jour d'Ubuntu 24.04 à 26.04 sur un serveur avec #incus : attention, les nouvelles sécurités par défaut d' AppArmor cassent tout ! La solution ici : https://discuss.linuxcontainers.org/t/issues-in-ubuntu-26-04-apt-not-working-in-unprivileged-lxcs/26591
-
A big limitation for #incus coming from #cloudinit: it is impossible to properly merge cloud-config keys between user-data and vendor-data. Even after setting merging rules, the user-data key content will override the vendor-data one.
So e.g. it is impossible to use the `packages:` key in both to install default and instance-specific package.
The bug report exposes that the merging feature of cloud-init is of dubious quality: https://github.com/canonical/cloud-init/issues/6268
This is quite annoying.
-
JumpyVi is iterating on the Bluefin developer mode. #incus support is going to slay out on this one!
-
JumpyVi is iterating on the Bluefin developer mode. #incus support is going to slay out on this one!
-
JumpyVi is iterating on the Bluefin developer mode. #incus support is going to slay out on this one!
-
JumpyVi is iterating on the Bluefin developer mode. #incus support is going to slay out on this one!
-
JumpyVi is iterating on the Bluefin developer mode. #incus support is going to slay out on this one!
-
Kapsule: it shipped and nobody died
"In my last post , I laid out the vision for Kapsule—a container-based extensibility layer for KDE Linux built on top of Incus."
I really like what's happening here. This might be of good use for other distros as well.
Link: https://blog.lasath.org/2026/02/kapsule-it-shipped-and-nobody-died.html?m=1