-
-
Notifications
You must be signed in to change notification settings - Fork 123
[FEAT] Install controller's .deb
during image build process
#186
Comments
The alternative is 3-5 minute startups for users affected by the overlayfs cow bug. FWIW it doesn't install on every restart, only on recreation of the container. |
Hm, but I guess to workaround this limitation I could add a mount for that dir but that doesn't feel right 🤔. (I'm running this on k3s cluster FWIW) |
A restart persists the container filesystem. |
Correct, it should not be mounted. What this approach gives us, is one less interaction with files on startup, as the alternative is chowning a decent amount of files. |
When running as a plain container, yes. When running on k8s, nope. |
That is true, however we will stick to the current implementation, as that caters to the largest amount of our users. |
Is this a new feature request?
Wanted change
I've noticed that controller's image that is downloaded during the image build process in here:
docker-unifi-controller/Dockerfile
Lines 33 to 35 in 21a3e69
.deb
has to be installed on every container restart.This is especially noticeable on slower hardware like Raspberry PI (with slow IO). In the logs below notice that installing takes around 20 seconds and takes between 2 to 4 cores during that time.
Reason for change
Slow container startup.
Proposed code change
Install the
.deb
during process build and remove the installation service atdocker-unifi-controller/root/etc/cont-init.d/15-install
Lines 3 to 7 in 21a3e69
The text was updated successfully, but these errors were encountered: