fix(rootless): don't start docker before its network override is written

Initial rootless setup ran 'systemctl --user start docker' immediately
after install, but the rootless net/port-driver override.conf (and the
daemon-reload that loads it) aren't written until further down. So the
first start always failed — 'Job for docker.service failed' plus a
spurious '✗ Error Setting up Rootless' in the error report — even though
the later 'systemctl --user restart docker' brought the daemon up fine
once the override was in place.

Drop the premature start from the install step (keep install + enable);
the restart after the override is written is now the first real start.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: librelad <librelad@digitalangels.vip>

scripts/docker/install/rootless/rootless_docker.sh

@@ -101,10 +101,17 @@ installDockerRootless()
         local result; result=$(runSystem loginctl enable-linger $CFG_DOCKER_INSTALL_USER)
         checkSuccess "Adding automatic start (linger)"
 
-            # Rootless Install
+            # Install rootless Docker and enable the user service, but do NOT
+            # start it here. The rootless network override (override.conf,
+            # written further down) and the daemon-reload that picks it up
+            # haven't happened yet, so a start at this point comes up with no
+            # valid net/port-driver config and fails ("Job for docker.service
+            # failed") — a guaranteed, harmless first-start error that only
+            # noises the error report. The first real start is the
+            # `systemctl --user restart docker` below, once the override is in
+            # place.
 rootless_install=$(cat <<EOF
     curl -fsSL https://get.docker.com/rootless | sh && \
-    systemctl --user start docker && \
     systemctl --user enable docker && \
     exit
 EOF