Web terminal

Use the web terminal to inspect files, run commands, and troubleshoot a running application from Console.

Before you beginCopy Anchor Link

• Sign in to Console with an active account.
• You need Container Engine Admin, General Admin or General Owner for the project, either assigned directly or inherited from the workspace. Viewer and Editor cannot open a terminal.
• The application must be running and its image must contain /bin/sh.
• Applications with multiple running replicas and preview deployments are not supported.

Commands run with the user configured by the container image or application. Opening a terminal does not grant additional privileges.

Open a terminalCopy Anchor Link

1. Select your workspace and project.
2. Open Container Engine and select the application.
3. Select Terminal, then Connect.
4. Wait for the terminal to connect before entering commands.

You can type commands, paste text, use control keys, and resize the terminal. Commands affect the running application; check them before execution, especially when changing or deleting files.

Disconnect and reconnectCopy Anchor Link

Select Disconnect, exit the shell, or leave the Terminal page to close the connection. Reconnecting opens a new session. Previous output and sessions are not restored.

Stop long-running commands before disconnecting. Closing the terminal does not guarantee that commands or background processes already started inside the container have stopped.

Session limitsCopy Anchor Link

• You can have one active terminal session at a time.
• A session closes after fifteen minutes without keyboard input or pasted commands. Output alone does not keep it active.
• Each session lasts up to 30 minutes. Select Connect to start another session after it ends.
• Losing account or project access can end an active session.

TroubleshootingCopy Anchor Link

If the terminal cannot connect:

1. Confirm that the application is running and no start, restart, or deployment is still in progress.
2. Check that you have the required workspace or project role.
3. Confirm that the application image includes /bin/sh and has a single running instance.
4. Close any other terminal session, then select Connect again.

If the connection closes during use, check whether the application restarted or the session reached its time limit. Reconnect when the application is available.

For persistent failures or a message that the terminal is unavailable, contact support with the resource ID, approximate time, and displayed error. Exclude passwords, tokens, and other secrets.