for networking i check what i previously edited when i initially was setting up.
in addition to what i mentioned,
source
so i checked the file, it is still
# SPDX-License-Identifier: MIT-0
#
# This config file is installed as part of systemd.
# It may be freely copied and edited (following the MIT No Attribution license).
#
# To make local modifications, one of the following methods may be used:
# 1. add a drop-in file that extends this file by creating the
# /etc/systemd/network/80-container-host0.network.d/ directory and creating a
# new .conf file there.
# 2. copy this file into /etc/systemd/network or one of the other paths checked
# by systemd-networkd and edit it there.
# This file should not be edited in place, because it'll be overwritten on upgrades.
# This network file matches the container-side of the virtual Ethernet link
# created by systemd-nspawn's --network-veth switch. See systemd-nspawn(1) for
# details.
[Match]
Virtualization=container
Name=host0
[Network]
DHCP=false
Address=192.168.0.24/24
Gateway=192.168.0.2
LinkLocalAddressing=no
LLDP=yes
EmitLLDP=customer-bridge
[DHCP]
UseTimezone=yes
so that seems to be correct.
the other setting i checked is truenas networking. these are the active interfaces
enp19s0
br1 = 192.168.0.210/24
vb-docker
192.168.0.210 is for truenas ip. for docker it’s suppose to be 192.168.0.24
note: this br1 i can’t remember if it’s suppose to be 24 or 210. when i tested 192.168.0.24 test, i didn’t see any improvement, so i figured that doesn’t work if i edit there. so i figured just having the static ip set to 24 is at the 80-container-host0.network file
but when i check 192.168.0.24:5001 for dockge, it don’t load.
so i went to shell did a
jlmkr list, jlmkr status docker
jlmkr shell docker
then docker ps
it says jlmkr is running, the jailmaker docker is running. and the container is all running. so not sure what part broke or how to fix x-x;
problem began after the recent update