the docs for the imagebuilder state that one can disable services:
DISABLED_SERVICES The names of services from /etc/init.d to disable, e.g. dhcp for dnsmasq
I am building an image for a "dumb access point", aka it does not need DHCP or a firewall. However, when adding firewall into this variable, I get an error during build:
1+0 records in
1+0 records out
128 bytes copied, 5.5379e-05 s, 2.3 MB/s
Calculating checksums...
make[1]: *** No rule to make target 'firewall'. Stop.
Is this a known issue? Is the firewall service to important to be disabled?
For the record, I could successfully add dhcp into that variable and it did not error out.
I have three devices, two of them are dumb APs. And both of them have little space. So removing some packages and having enough space for python3-light (to allow administration via Ansible) is really nice.
This part already works flawlessly for all three of them. But each time I upgrade I have the unnecessary services enabled again, so I wanted to try out what the docs promise...
Using a - prefix for a package name allows removing the package from an image built using imagebuilder. Or rather, it prevents its installation in the image.
However, that does not seem to fully work for some "important" packages. I do not need DHCP or firewall on my dumb APs, so I tried to exclude them in the image:
But some of them still end up in the image. The PPOE packages do not seem to be present, same for the odhcp6c ones. However, dnsmasq and firewall are both present.
Do I need to put the excluded packages at the end of the list?
There was a thread a while ago about the packages which cannot be removed with the IB and will require compiling from scratch to remove. Giving the limitations of the IB, maybe you should use the uci-defaults script to stop/disable services from running on first boot.