umbrelOS 1.5 GPU acceleration support #4523
Triggered via pull request
October 10, 2025 16:50
lukechilds
lukechilds
opened
#3771
Status
Failure
Total duration
13s
Artifacts
–
Annotations
8 errors and 4 notices
|
Lint apps
❌ Linting failed with 7 errors ❌
|
|
1:
sabnzbd/umbrel-app.yml#L49
Invalid input
|
|
0:
portainer/umbrel-app.yml#L70
Invalid input
|
|
1:
plex/umbrel-app.yml#L31
Invalid input
|
|
1:
jellyfin/umbrel-app.yml#L56
Invalid input
|
|
0:
immich/umbrel-app.yml#L80
Invalid input
|
|
0:
frigate/umbrel-app.yml#L48
Invalid input
|
|
1:
emby/umbrel-app.yml#L62
Invalid input
|
|
Potentially using unsafe user in service "web":
frigate/docker-compose.yml#L0
The default container user "root" can lead to security vulnerabilities. If you are using the root user, please try to specify a different user (e.g. "1000:1000") in the compose file or try to set the UID/PUID and GID/PGID environment variables to 1000.
|
|
External port mapping "8555:8555/udp":
frigate/docker-compose.yml#L23
Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
|
|
External port mapping "8555:8555/tcp":
frigate/docker-compose.yml#L23
Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
|
|
External port mapping "8554:8554":
frigate/docker-compose.yml#L23
Port mappings may be unnecessary for the app to function correctly. Docker's internal DNS resolves container names to IP addresses within the same network. External access to the web interface is handled by the app_proxy container. Port mappings are only needed if external access is required to a port not proxied by the app_proxy, or if an app needs to expose multiple ports for its functionality (e.g., DHCP, DNS, P2P, etc.).
|