mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-19 02:28:59 +00:00
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:
parent
4ac518a020
commit
e5faca5035
4 changed files with 19 additions and 20 deletions
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue