I have 3 containers all set to start-on-boot. However, upon boot, the first one never auto starts, but the rest do. I’m seeing with with the 7.7 beta and RC. There are no log messages indicating any sort of failure to start either. I haven’t tried 7.6 because I only have one device available for testing right now. My first container works fine when I manually start it, and if I delete and recreate my first container (thus moving it from first to last), upon rebooting it works properly and the new container doesn’t.
Exporting doesn’t seem to export the actual containers, but it’s Adguard Home, Knot, and networkboot/dhcpd.
/container mounts
add dst=/opt/adguardhome/work name=adguard_work src=/sata1-part1/containers/adguard/work
add dst=/opt/adguardhome/conf name=adguard_conf src=/sata1-part1/containers/adguard/conf
add dst=/config name=knot_config src=/sata1-part1/containers/knot/config
add dst=/storage name=knot_storage src=/sata1-part1/containers/knot/storage
add dst=/rundir name=knot_rundir src=/sata1-part1/containers/knot/rundir
add dst=/data name=dhcp_data src=/sata1-part1/containers/dhcp/data
/container
add cmd="knotd -v -c /config/knot.conf" envlist=knot_envs hostname=knot interface=veth_knot logging=yes mounts=knot_config,knot_storage,knot_rundir root-dir=\
sata1-part1/container-roots/knot start-on-boot=yes
add envlist=dhcp_envs hostname=dhcp interface=veth_dhcp logging=yes mounts=dhcp_data root-dir=sata1-part1/container-roots/dhcp start-on-boot=yes
add envlist=adguard_envs hostname=adguard interface=veth_adguard logging=yes mounts=adguard_work,adguard_conf root-dir=sata1-part1/container-roots/adguard \
start-on-boot=yes workdir=/opt/adguardhome/work
/container config
set registry-url=https://registry-1.docker.io tmpdir=sata1-part1/pull