Skip to content

add chromium browser app #1191

add chromium browser app

add chromium browser app #1191

Triggered via pull request December 7, 2024 05:40
@maddog1110maddog1110
synchronize #1888
Status Failure
Total duration 14s
Artifacts

lint-apps.yml

on: pull_request_target
Lint apps
6s
Lint apps
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 1 warning, and 2 notices
Invalid image name "lscr.io/linuxserver/chromium:version-14193214": chromium-browser/docker-compose.yml#L4
Images should be named like "<name>:<version-tag>@<sha256>"
Lint apps
❌&nbsp;&nbsp;&nbsp;Linting failed with 1 error&nbsp;&nbsp;&nbsp;❌
Lint apps
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
External port mapping "3000:3000": chromium-browser/docker-compose.yml#L15
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 "3001:3001": chromium-browser/docker-compose.yml#L15
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.).