❌   Linting failed with 3 errors and 2 warnings   ❌

YAMLParseError: Map keys must be unique at line 12, column 5: container_name: wordpress_app_1 image: wordpress:6.9.1@sha256:1b5fee9f90d12c7fcba8b0bcb0f9d94166daa1086b755… ^

YAMLParseError: Map keys must be unique at line 12, column 5: container_name: nginx-proxy-manager_web_1 image: jc21/nginx-proxy-manager:2.14.0@sha256:2aa69b382a384b676c0d4f1d6f2ea… ^

Too big: expected string to have <=5000 characters

The APP_HOST environment variable must be set to the hostname of the app_proxy container (e.g. "<app-id>_<web-container-name>_1").

The restart policy of the container "electrs" should be set to "on-failure".

The volume "${APP_DATA_DIR}/data/logs:/app/logs" tries to mount the file/directory "/datum/data/logs", but it is not present. This can lead to permission errors!

The volume "${APP_DATA_DIR}/data/settings/:/app/conf/" tries to mount the file/directory "/datum/data/settings/", but it is not present. This can lead to permission errors!

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.

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.

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.).

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.).

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.).

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.).

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!