- Deploy a container group.
- Navigate into the container group deployment.
- Click on a running replica. You’re not able to interact with a deployment that is still starting.
- You’ll see the terminal window on this page, along with controls for the replica allowing you to restart, recreate, or reallocate the deployment, along with seeing logs.
- If you’re having issues getting the Terminal to load, try closing additional Portal tabs and windows, and hard-refreshing the page with CTRL/CMD+SHIFT+R.
- If the above steps don’t work, try re-allocating the replica to a new node.
- If you suddenly lose access to the terminal, it’s possible the replica went offline or was re-allocated. Try heading back to the deployment page and see if the node is still online.
- Some container images will exit if no command is specified, resulting in repeated failures and reallocations, and you will not be able to interact with it using the terminal. If you wish to interact with a terminal in one of these containers, adding a command of sleep with an argument of infinity will usually ensure the container stays running and you can access the terminal.