Skip to content

Update Elements Core to v23.2.4 & PeerSwap to v4rc2 #1230

Update Elements Core to v23.2.4 & PeerSwap to v4rc2

Update Elements Core to v23.2.4 & PeerSwap to v4rc2 #1230

Triggered via pull request December 15, 2024 01:20
@Impa10rImpa10r
synchronize #1926
Status Success
Total duration 15s
Artifacts

lint-apps.yml

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

Annotations

1 warning and 5 notices
Lint apps
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Mounted file/directory "/elements/torrc" doesn't exist: elements/docker-compose.yml#L64
The volume "${APP_DATA_DIR}/torrc:/etc/tor/torrc:ro" tries to mount the file/directory "/elements/torrc", but it is not present. This can lead to permission errors!
External port mapping "$APP_ELEMENTS_NODE_RPC_PORT:$APP_ELEMENTS_NODE_RPC_PORT": elements/docker-compose.yml#L13
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 "$APP_ELEMENTS_NODE_P2P_PORT:$APP_ELEMENTS_NODE_P2P_PORT": elements/docker-compose.yml#L13
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 "node": elements/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.
Potentially using unsafe user in service "web": elements/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.