Update mattermost to version v11.4.2 #6496
Annotations
2 errors and 2 notices
|
Lint apps
❌ Linting failed with 1 error ❌
|
|
Invalid image name "alexlack/mattermost-db:v11.4.2@sha256:2f4dec24e45032094a1b96a6078bddf67884390683f75ba8dad6b8e4bf95d7e3":
mattermost/docker-compose.yml#L35
Error: HTTP 404 for alexlack/mattermost-db:v11.4.2@sha256:2f4dec24e45032094a1b96a6078bddf67884390683f75ba8dad6b8e4bf95d7e3: {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":"unknown manifest name=alexlack/mattermost-db revision=sha256:2f4dec24e45032094a1b96a6078bddf67884390683f75ba8dad6b8e4bf95d7e3"}]}
|
|
External port mapping "8443:8443/udp":
mattermost/docker-compose.yml#L27
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 "8443:8443/tcp":
mattermost/docker-compose.yml#L27
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.).
|