Community discussions

MikroTik App
 
nofdak
just joined
Topic Author
Posts: 12
Joined: Thu May 28, 2020 3:10 am

First Container in list doesn't start on boot

Mon Dec 19, 2022 10:32 pm

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
 
User avatar
sirbryan
Member Candidate
Member Candidate
Posts: 298
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:

Re: First Container in list doesn't start on boot

Tue Dec 20, 2022 6:15 am

I've observed this as well on my CCR2116 on 7.6. Pi Hole (was the only and now) is the first container and it doesn't start automatically despite being set.

Until this week, that machine didn't have any other containers, so I haven't verified if the others do start on boot.
 
AUsquirrel
newbie
Posts: 39
Joined: Fri Feb 21, 2014 10:28 pm

Re: First Container in list doesn't start on boot

Fri Dec 30, 2022 11:15 pm

I also have seen the same issue with container 0.
 
ajgnet
newbie
Posts: 35
Joined: Wed Apr 27, 2022 1:57 am

Re: First Container in list doesn't start on boot

Sat Dec 31, 2022 1:19 pm

Reporting the same issue
 
elico
Member Candidate
Member Candidate
Posts: 143
Joined: Mon Nov 07, 2016 3:23 am

Re: First Container in list doesn't start on boot

Tue Jan 10, 2023 4:34 am

Reporting the same issue
Has anyone tested this with 7.7rc?
 
lnc1995
just joined
Posts: 3
Joined: Sat Dec 10, 2022 1:48 am

Re: First Container in list doesn't start on boot

Thu Jan 26, 2023 11:47 pm

Same issue. 7.6 stable and 7.7 stable tested.I have two containers,once i set two start-on-boot,there always a container doesn't start and no any error log.
 
lnc1995
just joined
Posts: 3
Joined: Sat Dec 10, 2022 1:48 am

Re: First Container in list doesn't start on boot

Thu Jan 26, 2023 11:52 pm

Found 7.8 beta2 fix this bug

Who is online

Users browsing this forum: No registered users and 2 guests