ericblade · October 23, 2024 07:13
diff --git a/gistfile1.txt b/gistfile1.txt
 First, get yourself a docker package.  https://github.com/JediNite/docker-ce-WDEX4100-binaries/releases/

 Get yourself some disk space on the NAS.  
 I did not seem to have enough disk space on mine, so I symlinked a directory from one of my connected harddrives into /usr/local/docker.
 Undo the tarball into /usr/local/docker.

 You'll probably need extra space in /var/lib/docker, so symlink that to somewhere on one of your hard drives.

 Add a group for docker.  Since the device is missing the 'groupadd' command, but you have root access, go and edit the /etc/groups file
 and get yourself a new docker group.

 add /usr/local/docker to your PATH  (export PATH=$PATH;/usr/local/docker)

 run dockerd

 > failed to start daemon: Devices cgroup isn't mounted

 inexplicably, cgroup-umount && cgroup-mount seemed to get through this

 run dockerd

 > failed to find ip table 'nat'

 run dockerd --iptables=false &

 docker pulls now work, but running 
 a container blows up with pair interfaces: operation not supported.



 .... looks like we're gonna need a kernel with veth .. but wd does not appear to provide the kernel config necessary to operate... so that might be a difficult task.

 ope!  we can run 'dockerd --iptables=false --bridge=none &' and then we can start containers with --network=host !

 Hooray!

 .... this probably means i won't be able to run a VPN without getting a kernel that supports VETH, but I doubt that's a possibility... sigh.

 also with only about 40MB free on the host disk right now (what??) i'm going to need to get more space allocated for docker images


 hello-world works, not sure if anything else does.  portainer seems to explode with containerd blowing lots of cgroups messages.

 gluetun comes up, but apparently running it with network=host blows up the host's network.  i can access it from the lan, but it can no longer access anything outside the lan.  so.... that's probably not good.  guess i'll find out sometime soon if the configuration of everything persists, or if it's aall lost on reboot.
	First, get yourself a docker package. https://github.com/JediNite/docker-ce-WDEX4100-binaries/releases/

	Get yourself some disk space on the NAS.
	I did not seem to have enough disk space on mine, so I symlinked a directory from one of my connected harddrives into /usr/local/docker.
	Undo the tarball into /usr/local/docker.

	You'll probably need extra space in /var/lib/docker, so symlink that to somewhere on one of your hard drives.

	Add a group for docker. Since the device is missing the 'groupadd' command, but you have root access, go and edit the /etc/groups file
	and get yourself a new docker group.

	add /usr/local/docker to your PATH (export PATH=$PATH;/usr/local/docker)

	run dockerd

	> failed to start daemon: Devices cgroup isn't mounted

	inexplicably, cgroup-umount && cgroup-mount seemed to get through this

	run dockerd

	> failed to find ip table 'nat'

	run dockerd --iptables=false &

	docker pulls now work, but running
	a container blows up with pair interfaces: operation not supported.



	.... looks like we're gonna need a kernel with veth .. but wd does not appear to provide the kernel config necessary to operate... so that might be a difficult task.

	ope! we can run 'dockerd --iptables=false --bridge=none &' and then we can start containers with --network=host !

	Hooray!

	.... this probably means i won't be able to run a VPN without getting a kernel that supports VETH, but I doubt that's a possibility... sigh.

	also with only about 40MB free on the host disk right now (what??) i'm going to need to get more space allocated for docker images


	hello-world works, not sure if anything else does. portainer seems to explode with containerd blowing lots of cgroups messages.

	gluetun comes up, but apparently running it with network=host blows up the host's network. i can access it from the lan, but it can no longer access anything outside the lan. so.... that's probably not good. guess i'll find out sometime soon if the configuration of everything persists, or if it's aall lost on reboot.