App Submission: Zoraxy - Reverse Proxy Manager #1089
Triggered via pull request
November 21, 2024 08:33
dennysubke
synchronize
#1751
Status
Success
Total duration
17s
Artifacts
–
Annotations
1 warning and 4 notices
"icon" and "gallery" needs to be empty for new app submissions:
zoraxy/umbrel-app.yml#L55
The "icon" and "gallery" fields must be empty for new app submissions as it is being created by the Umbrel team.
|
Mounted file/directory "/zoraxy/data/config/" doesn't exist:
zoraxy/docker-compose.yml#L14
The volume "${APP_DATA_DIR}/data/config/:/opt/zoraxy/config" tries to mount the file/directory "/zoraxy/data/config/", but it is not present. This can lead to permission errors!
|
External port mapping "41080:80":
zoraxy/docker-compose.yml#L11
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 "41443:443":
zoraxy/docker-compose.yml#L11
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.).
|
Potentially using unsafe user in service "server":
zoraxy/docker-compose.yml#L1
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.
|