# /etc/init.d/firewall restart
Warning: Unable to locate ipset utility, disabling ipset support
Warning: Section @defaults[0] requires unavailable target extension FLOWOFFLOAD, disabling
Warning: Section @defaults[0] requires unavailable target extension FLOWOFFLOAD, disabling
* Set tcp_ecn to off
* Set tcp_syncookies to on
* Set tcp_window_scaling to on
* Running script '/etc/firewall.user'
Evidently there is something weird going on with the firewall as well as the image, since service is missing. As I am not experienced with container installation, I'll refer it to some other members of the forum and hopefully you'll get more lucky.
Just mention where did you get the image from.
above is about the 'service' function from /etc/profile not existing
lxc is probably similar to qemu in that the init process is 'special'... but pretty sure that kind of stuff would be mentioned where you downloaded your stuff
afaik, when you run openwrt in qemu and probably lxc certain changes need to be made to the way somethings startup...
not an expert in this area but it should be explained where the dude downloaded his image... as they probably made all the necessary modifications or some or none... answer changes depending on that...
i.e.; this message;
is probably referring to the lxc host-os kernel... etc. etc.
Probably you are lxc-attaching right? Because attach notoriously doesn't export all paths and variables. It's the same for me. If you go over ssh, and I guess lxc-console as well, it's everything in place tho.
As also @anon50098793 said, that's related to the host kernel.Kernels from major distros (at least Debian based) appear to work well without any specific tuning, at least i had no issues so far. And in any case it's just a warning, should be safe to ignore.
did you keep settings / restore a backup file across those versions?
I tried with restore, and with manual setup from scratch. Same result both times.
Probably you are lxc-attaching right? Because attach notoriously doesn't export all paths and variables. It's the same for me. If you go over ssh, and I guess lxc-console as well, it's everything in place tho.
Great point. That's right. I use LXD, so it's lxc exec but this is just a wrapper for lxc commands.
So after logging through ssh, I got a correct response from the service: https://pastebin.com/raw/ygH5Agfu
Just to close this: the problem was rendered moot by installing OpenWRT with a 22.03 LXD image which became available in the meantime in the official LXD repo.