Incus - Revision history

Diskette: Diskette moved page Docs:Incus to Incus

2026-03-27T14:01:09Z

Diskette moved page Docs:Incus to Incus

← Older revision		Revision as of 21:01, 27 March 2026
(No difference)

Diskette at 22:39, 10 June 2025

2025-06-10T22:39:30Z

← Older revision		Revision as of 05:39, 11 June 2025
Line 41:		Line 41:
	$PORTCONNECT is the port on the container that it'll connect to		$PORTCONNECT is the port on the container that it'll connect to

	$IPLISTEN is a valid IPv4 address '''that your main ~~machines connect~~ to'''		$IPLISTEN is a valid IPv4 address '''that your main machine is assigned to'''

	$IPCONNECT just leave this to 0.0.0.0 </blockquote>For example, Thetic has an internal network of 10.10.10.2 and a container called internal. Inside that container, there is an HTTP server listening on port 8303 and we actually want to get to that port from the outside world.		$IPCONNECT just leave this to 0.0.0.0 </blockquote>For example, Thetic has an internal network of 10.10.10.2 and a container called internal. Inside that container, there is an HTTP server listening on port 8303 and we actually want to get to that port from the outside world.
	incus config device add internal tcp8303-8303 proxy listen=tcp:10.10.10.2:8303 connect=tcp:0.0.0.0:8303 nat=true		incus config device add internal tcp8303-8303 proxy listen=tcp:10.10.10.2:8303 connect=tcp:0.0.0.0:8303 nat=true

Diskette at 16:28, 8 June 2025

2025-06-08T16:28:55Z

← Older revision		Revision as of 23:28, 8 June 2025
Line 25:		Line 25:

	To do so,		To do so,
	incus config device override ~~set~~ $CONTAINER $NETWORKDEVICE ipv4.address=$IPADDRESS		incus config device override $CONTAINER $NETWORKDEVICE ipv4.address=$IPADDRESS
	Where<blockquote>$CONTAINER is the container name		Where<blockquote>$CONTAINER is the container name

Diskette at 15:51, 2 June 2025

2025-06-02T15:51:25Z

← Older revision		Revision as of 22:51, 2 June 2025
Line 31:		Line 31:

	$IPADDRESS a valid IPv4 address from CIDR range</blockquote>For example, if I wanted to set internal container to have an IPv4 of 10.9.12.2 inside the network device eth0, I execute the command		$IPADDRESS a valid IPv4 address from CIDR range</blockquote>For example, if I wanted to set internal container to have an IPv4 of 10.9.12.2 inside the network device eth0, I execute the command
	incus config device override ~~set~~ internal eth0 ipv4.address=10.9.12.2		incus config device override internal eth0 ipv4.address=10.9.12.2

	==== Actual port forwarding ====		==== Actual port forwarding ====

Diskette at 15:46, 2 June 2025

2025-06-02T15:46:29Z

← Older revision		Revision as of 22:46, 2 June 2025
Line 2:		Line 2:

	Why Incus? Well, it was the closest thing to FreeBSD Jails for me... I love FreeBSD Jails, man. But FreeBSD CPU performance sucks-butt. I just want a space for application isolation. But Docker fucks with my firewall and eats my memory so that ain't feasible as well. I hate all of the Docker-like solution, I just want to have FreeBSD Jails on Linux. We used to use systemd-nspawn as well, but that solution also kinda sucked. <sup>Please just give me a simple isolation application like FreeBSD Jails does, please.</sup>		Why Incus? Well, it was the closest thing to FreeBSD Jails for me... I love FreeBSD Jails, man. But FreeBSD CPU performance sucks-butt. I just want a space for application isolation. But Docker fucks with my firewall and eats my memory so that ain't feasible as well. I hate all of the Docker-like solution, I just want to have FreeBSD Jails on Linux. We used to use systemd-nspawn as well, but that solution also kinda sucked. <sup>Please just give me a simple isolation application like FreeBSD Jails does, please.</sup>

			== Setting up ==
			To set-up, do <code>incus admin init</code> and a voila, done.

			Give yourself <code>incus-admin</code> user group

			I think [[User:Techit]] installed web UI for Thetic Incus, but I don't use that. So.

			== Networking ==
			<small>Please clean this up later by using OVN/OVS</small>

			How the fuck does Incus does their networking, I have no idea.

			But basically, the default eth0 is a bridge to your actual network, it is running an internal DHCP server using dnsmasq with random private CIDR range assigned to it (e.g., <code>10.52.21.1/24</code> or <code>10.63.183.1/24</code>).

			When you connect (I.E., creating a new container with the default profile), a random IPv4 address from that private CIDR range will get assigned to that container. But however, don't be fooled, it's still not static IP.

			=== Port forwarding ===

			==== Setting a static IPv4 address ====
			In order to do port forward [other than the older way that it isn't an actual NAT, and sees every request as a loopback (127.0.0.1),] you would have to manually assign a valid IPv4 address from that private CIDR.

			To do so,
			incus config device override set $CONTAINER $NETWORKDEVICE ipv4.address=$IPADDRESS
			Where<blockquote>$CONTAINER is the container name

			$NETWORKDEVICE is the network device

			$IPADDRESS a valid IPv4 address from CIDR range</blockquote>For example, if I wanted to set internal container to have an IPv4 of 10.9.12.2 inside the network device eth0, I execute the command
			incus config device override set internal eth0 ipv4.address=10.9.12.2

			==== Actual port forwarding ====
			incus config device add internal $PROTOCOL$PORTLISTEN-$PORTCONNECT proxy listen=$PROTOCOL:$IPLISTEN:$PORTLISTEN connect=$PROTOCOL:$IPCONNECT:PORTCONNECT nat=true
			Where<blockquote>$PROTOCOL is the protocol (tcp, udp, unix)

			$PORTLISTEN is the port on the main machine that the container is running on that will listen to

			$PORTCONNECT is the port on the container that it'll connect to

			$IPLISTEN is a valid IPv4 address '''that your main machines connect to'''

			$IPCONNECT just leave this to 0.0.0.0 </blockquote>For example, Thetic has an internal network of 10.10.10.2 and a container called internal. Inside that container, there is an HTTP server listening on port 8303 and we actually want to get to that port from the outside world.
			incus config device add internal tcp8303-8303 proxy listen=tcp:10.10.10.2:8303 connect=tcp:0.0.0.0:8303 nat=true

Diskette: Created page with "Hello there 🙂 🙂 🙂 🙂 🙂 🙂 (This is supposed to denote "sarcastic smile"). Welcome to Incus documentation page, where we use incorrect terminologies for networking and stuff, I guess. Why Incus? Well, it was the closest thing to FreeBSD Jails for me... I love FreeBSD Jails, man. But FreeBSD CPU performance sucks-butt. I just want a space for application isolation. But Docker fucks with my firewall and eats my memory so that ain't feasible as well. I hate..."

2025-05-27T19:08:52Z

Created page with "Hello there 🙂 🙂 🙂 🙂 🙂 🙂 (This is supposed to denote "sarcastic smile"). Welcome to Incus documentation page, where we use incorrect terminologies for networking and stuff, I guess. Why Incus? Well, it was the closest thing to FreeBSD Jails for me... I love FreeBSD Jails, man. But FreeBSD CPU performance sucks-butt. I just want a space for application isolation. But Docker fucks with my firewall and eats my memory so that ain't feasible as well. I hate..."

New page

Hello there 🙂 🙂 🙂 🙂 🙂 🙂 (This is supposed to denote "sarcastic smile"). Welcome to Incus documentation page, where we use incorrect terminologies for networking and stuff, I guess.

Why Incus? Well, it was the closest thing to FreeBSD Jails for me... I love FreeBSD Jails, man. But FreeBSD CPU performance sucks-butt. I just want a space for application isolation. But Docker fucks with my firewall and eats my memory so that ain't feasible as well. I hate all of the Docker-like solution, I just want to have FreeBSD Jails on Linux. We used to use systemd-nspawn as well, but that solution also kinda sucked. <sup>Please just give me a simple isolation application like FreeBSD Jails does, please.</sup>