mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-08-20 11:57:19 +02:00
Updater bot : webtop_kde updated to 4.16-r0-ls94
This commit is contained in:
@@ -1,3 +1,6 @@
|
|||||||
|
|
||||||
|
## 4.16-r0-ls94 (2026-08-01)
|
||||||
|
- Update to latest version from linuxserver/docker-webtop (changelog : https://github.com/linuxserver/docker-webtop/releases)
|
||||||
## 4.16-r0-ls93.2 (28-07-2026)
|
## 4.16-r0-ls93.2 (28-07-2026)
|
||||||
|
|
||||||
- Fix Selkies dying with a Rust `RuntimeDirNotSet` unwrap panic just after `Data WebSocket Server listening on port 8081`, and the data websocket then being proxied to the wrong port. Upstream relies on s6-rc ordering: `init-selkies-config` publishes `XDG_RUNTIME_DIR` and `CUSTOM_WS_PORT` into the s6 envdir and `svc-selkies` starts afterwards. The add-on entrypoint replaces s6-overlay and starts every `s6-rc.d` run script in parallel with no dependency graph, so Selkies can snapshot the envdir before that oneshot has written to it -- which is why it bound port 8081 (its own default) instead of the 8082 nginx proxies to, and why its Wayland compositor found no runtime directory to bind a socket in. `20-folders.sh` now exports both variables inside each run script, where no start ordering can lose them, and corrects the base image's `$HOME/.XDG` override where that write happens instead of appending a correction after the `exit 0` that the oneshot-tolerance block adds -- which meant the correction never ran on any boot after the first.
|
- Fix Selkies dying with a Rust `RuntimeDirNotSet` unwrap panic just after `Data WebSocket Server listening on port 8081`, and the data websocket then being proxied to the wrong port. Upstream relies on s6-rc ordering: `init-selkies-config` publishes `XDG_RUNTIME_DIR` and `CUSTOM_WS_PORT` into the s6 envdir and `svc-selkies` starts afterwards. The add-on entrypoint replaces s6-overlay and starts every `s6-rc.d` run script in parallel with no dependency graph, so Selkies can snapshot the envdir before that oneshot has written to it -- which is why it bound port 8081 (its own default) instead of the 8082 nginx proxies to, and why its Wayland compositor found no runtime directory to bind a socket in. `20-folders.sh` now exports both variables inside each run script, where no start ordering can lose them, and corrects the base image's `$HOME/.XDG` override where that write happens instead of appending a correction after the `exit 0` that the oneshot-tolerance block adds -- which meant the correction never ran on any boot after the first.
|
||||||
|
|||||||
@@ -2,11 +2,11 @@
|
|||||||
# ALEXBELGIUM'S DOCKERFILE #
|
# ALEXBELGIUM'S DOCKERFILE #
|
||||||
#============================#
|
#============================#
|
||||||
# _.------.
|
# _.------.
|
||||||
# _.-` ('>.-`"4.16-r0-ls93""-.
|
# _.-` ('>.-`"4.16-r0-ls94""-.
|
||||||
# '.--'` _'` _ .--.)
|
# '.--'` _'` _ .--.)
|
||||||
# -' '-.-';` `
|
# -' '-.-';` `
|
||||||
# ' - _.' ``'--.
|
# ' - _.' ``'--.
|
||||||
# '---` .-'"4.16-r0-ls93"`
|
# '---` .-'"4.16-r0-ls94"`
|
||||||
# /`
|
# /`
|
||||||
#=== Home Assistant Addon ===#
|
#=== Home Assistant Addon ===#
|
||||||
|
|
||||||
|
|||||||
@@ -143,5 +143,5 @@ slug: webtop
|
|||||||
tmpfs: true
|
tmpfs: true
|
||||||
udev: true
|
udev: true
|
||||||
url: https://github.com/alexbelgium/hassio-addons
|
url: https://github.com/alexbelgium/hassio-addons
|
||||||
version: "4.16-r0-ls93.2"
|
version: "4.16-r0-ls94"
|
||||||
video: true
|
video: true
|
||||||
|
|||||||
@@ -1,9 +1,9 @@
|
|||||||
{
|
{
|
||||||
"github_fulltag": "true",
|
"github_fulltag": "true",
|
||||||
"last_update": "2026-07-21",
|
"last_update": "2026-08-01",
|
||||||
"repository": "alexbelgium/hassio-addons",
|
"repository": "alexbelgium/hassio-addons",
|
||||||
"slug": "webtop",
|
"slug": "webtop",
|
||||||
"source": "github",
|
"source": "github",
|
||||||
"upstream_repo": "linuxserver/docker-webtop",
|
"upstream_repo": "linuxserver/docker-webtop",
|
||||||
"upstream_version": "4.16-r0-ls93"
|
"upstream_version": "4.16-r0-ls94"
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user