CI / check (pull_request) Successful in 18s
netork-ui ran nginx as root, and its entrypoint wrote the self-signed certificate into ssl_certs as root, the key at 0600. From NetOrk/netork#1389 on, nginx runs as netork, the API's user, and cannot read that key, so the UI would not start on any existing host. Before the containers are recreated, one container of the engine image of the version being deployed, as root with only CHOWN, runs `chown -Rc netork:netork /app/ssl`. -c names only what it changed, so a host handed over earlier sees nothing. A failure stops the deploy with the old containers running. Older engine images carry the same netork user, so deploying an older version stays possible.