fix: expose cln grpc port #1644
Triggered via pull request
February 11, 2025 18:09
jackstar12
jackstar12
synchronize
#2180
Status
Success
Total duration
14s
Artifacts
–
Annotations
10 notices
|
Mounted file/directory "/core-lightning/data/app" doesn't exist:
core-lightning/docker-compose.yml#L13
The volume "${APP_DATA_DIR}/data/app:${APP_CONFIG_DIR}" tries to mount the file/directory "/core-lightning/data/app", but it is not present. This can lead to permission errors!
|
|
Mounted file/directory "/core-lightning/torrc" doesn't exist:
core-lightning/docker-compose.yml#L92
The volume "${APP_DATA_DIR}/torrc:/etc/tor/torrc:ro" tries to mount the file/directory "/core-lightning/torrc", but it is not present. This can lead to permission errors!
|
|
External port mapping "${APP_CORE_LIGHTNING_REST_PORT}:${APP_CORE_LIGHTNING_REST_PORT}":
core-lightning/docker-compose.yml#L44
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_CORE_LIGHTNING_DAEMON_PORT}:9735":
core-lightning/docker-compose.yml#L60
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_CORE_LIGHTNING_WEBSOCKET_PORT}:${APP_CORE_LIGHTNING_WEBSOCKET_PORT}":
core-lightning/docker-compose.yml#L60
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 "${CORE_LIGHTNING_REST_PORT}:${CORE_LIGHTNING_REST_PORT}":
core-lightning/docker-compose.yml#L60
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_CORE_LIGHTNING_DAEMON_GRPC_PORT}:${APP_CORE_LIGHTNING_DAEMON_GRPC_PORT}":
core-lightning/docker-compose.yml#L60
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 "app":
core-lightning/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 "c-lightning-rest":
core-lightning/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 "lightningd":
core-lightning/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.
|