Fix Docker update copy to recreate the container instead of docker restart

docker restart reuses the image the container was created with, so the
pulled update never takes effect. Point users at docker compose pull &&
docker compose up -d, with pull/stop/rm and re-run for non-compose
installs, matching docs/DOCKER.md.
This commit is contained in:
rcourtman 2026-07-10 00:22:39 +01:00
parent 4ac518a020
commit e5faca5035
4 changed files with 19 additions and 20 deletions

View file

@ -191,10 +191,12 @@ Pulse can self-update to the latest stable version.
| Platform | Command |
|----------|---------|
| **Docker** | `docker pull rcourtman/pulse:vX.Y.Z && docker restart pulse` |
| **Docker** | `docker compose pull && docker compose up -d` |
| **Kubernetes** | `helm repo update && helm upgrade pulse pulse/pulse -n pulse` |
| **Systemd / Proxmox LXC** | `sudo /bin/update` |
Docker without Compose: `docker restart` keeps the old image running. Run `docker pull rcourtman/pulse:vX.Y.Z`, then `docker stop pulse && docker rm pulse` and re-run your original `docker run` command.
### Rollback
If an update causes issues on systemd installations, backups are created automatically during the update process.