Understand container networking
Inspect deployment networks and distinguish internal ports from public HTTPS access.
The Network page displays the Docker networks configured for the container's deployment destinations. It identifies the primary destination and any additional destinations. This page displays the current configuration; it does not provide a network editor.
Inspect connectivity
- Open the container and select Network.
- Review the destination and network information.
- When connecting to another project resource, check that resource's connection instructions and network requirements.
Do not assume that resources on different servers or imported networks share connectivity just because they are listed in the same project. Importing a container preserves its existing networks.
Find the internal hostname
Open the container's Overview and copy Internal hostname. Use this hostname and your application's listening port when connecting from another container on a shared, reachable internal network.
This field shows the configured hostname, not a live connectivity check. A deployment may be needed before configuration changes take effect. An em dash (—) means a managed hostname is unavailable for this container or deployment type.
The internal hostname does not provide public access and is not intended for connections from your local computer. Being in the same project alone does not guarantee a shared network.
Expose an HTTP application
Set Internal HTTP port to the application's listening port. This is a container port, not a host port mapping. Use the hostname shown in Domain & DNS for public HTTPS access.
See Configure domains and DNS for routing configuration and Configure a firewall policy to restrict access through the managed application route.