add chromium browser app #1194
Triggered via pull request
December 7, 2024 05:44
maddog1110
maddog1110
synchronize
#1888
Status
Failure
Total duration
15s
Artifacts
–
Annotations
3 errors, 2 warnings, and 2 notices
|
Invalid image name "lscr.io/linuxserver/chromium:stable":
chromium-browser/docker-compose.yml#L3
Images should be named like "<name>:<version-tag>@<sha256>"
|
|
Invalid image name "lscr.io/linuxserver/chromium:stable":
chromium-browser/docker-compose.yml#L3
Error: HTTP 404 for lscr.io/linuxserver/chromium:stable: {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown"}]}
|
|
Lint apps
❌ Linting failed with 2 errors and 1 warning ❌
|
|
Lint apps
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Invalid restart policy:
chromium-browser/docker-compose.yml#L16
The restart policy of the container "chromium" should be set to "on-failure".
|
|
External port mapping "3000:3000":
chromium-browser/docker-compose.yml#L12
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#L12
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.).
|