Containers
What This Is For
Section titled “What This Is For”Containers is the flat, cross-deployment list of every running container on your cluster — Odysseus-managed and (with the “show all” filter) unmanaged alike, each tagged with its owning deployment and stack, its health, and its uptime. It is where you go to exec into a running container or tail its logs directly, without navigating through the deployment that owns it first.
How You Get Here
Section titled “How You Get Here”Sidebar section Main → Containers.
What It Looks Like
Section titled “What It Looks Like”
What It Shows
Section titled “What It Shows”/containers (Containers)
Section titled “/containers (Containers)”deployments:containers.actions— “Actions”deployments:containers.all— “All”deployments:containers.clear-filter— “Clear filter”deployments:containers.clear-filters— “Clear filters”deployments:containers.container-id— “Container ID”deployments:containers.containers— “Containers”deployments:containers.containers-will-appear-here-when— “Containers will appear here when deployments are running.”deployments:containers.deployment— “Deployment:”deployments:containers.deployment-2— “Deployment”deployments:containers.exec— “Exec”deployments:containers.external— “External”deployments:containers.health— “Health”deployments:containers.loading-containers— “Loading containers…”deployments:containers.logs— “Logs”deployments:containers.managed— “Managed”deployments:containers.name— “Name”deployments:containers.no-containers— “No containers”deployments:containers.no-containers-match-the-selected— “No containers match the selected filter.”deployments:containers.no-matching-containers— “No matching containers”deployments:containers.not-available— “N/A”deployments:containers.odysseus— “Odysseus”deployments:containers.remove— “Remove”deployments:containers.show-all-containers-including-non— “Show all containers (including non-Odysseus)”deployments:containers.stack— “Stack:”deployments:containers.stack-2— “Stack”deployments:containers.status— “Status”deployments:containers.uptime— “Uptime”deployments:containers.view— “View”
/containers/:id (ContainerDetail)
Section titled “/containers/:id (ContainerDetail)”deployments:containerDetail.are-you-sure-you-want— “Are you sure you want to restart container”deployments:containerDetail.are-you-sure-you-want-2— “Are you sure you want to stop container”deployments:containerDetail.ask-athena— “Ask Athena”deployments:containerDetail.back-to-containers— “← Back to Containers”deployments:containerDetail.backoff-time— “Backoff Time:”deployments:containerDetail.cancel— “Cancel”deployments:containerDetail.check-container-logs-for-the— “Check container logs for the crash reason. Common causes: missing dependencies, incorrect entrypoint, or application errors.”deployments:containerDetail.click-load-logs-to-view— “Click "Load Logs" to view container logs.”deployments:containerDetail.command— “Command:”deployments:containerDetail.confirm-restart— “Confirm Restart”deployments:containerDetail.confirm-stop— “Confirm Stop”deployments:containerDetail.consecutive-failures-the-container-will— “consecutive failures, the container will be restarted automatically.”deployments:containerDetail.container— “Container:”deployments:containerDetail.container-id— “Container ID”deployments:containerDetail.container-in-crashloopbackoff— “⚠️ Container in CrashLoopBackOff”deployments:containerDetail.container-logs— “Container Logs”deployments:containerDetail.container-not-found— “Container not found.”deployments:containerDetail.container-was-killed-due-to— “Container was killed due to out of memory. It will restart automatically.”deployments:containerDetail.crash-loop-testing— “Crash Loop Testing”deployments:containerDetail.created— “Created”deployments:containerDetail.deployment— “Deployment”deployments:containerDetail.enter-a-command-above-to— “Enter a command above to execute it in the container.”deployments:containerDetail.enter-command-e-g-ls— “Enter command (e.g., ls /, echo test, pwd)”deployments:containerDetail.exec— “Exec”deployments:containerDetail.execute— “Execute”deployments:containerDetail.execute-command— “Execute Command”deployments:containerDetail.executing— “Executing…”deployments:containerDetail.exit-code— “Exit Code:”deployments:containerDetail.failure-threshold— “Failure Threshold”deployments:containerDetail.health-check-configuration— “Health Check Configuration”deployments:containerDetail.health-check-failure-simulation-is— “Health check failure simulation is active. The container will fail health checks until stopped.”deployments:containerDetail.health-check-simulation-testing— “Health Check Simulation (Testing)”deployments:containerDetail.health-status— “Health Status”deployments:containerDetail.interval— “Interval”deployments:containerDetail.load-logs— “Load Logs”deployments:containerDetail.loading— “Loading…”deployments:containerDetail.loading-container— “Loading container…”deployments:containerDetail.logs— “Logs”deployments:containerDetail.memory-limit-testing— “Memory Limit Testing”deployments:containerDetail.networks— “Networks”deployments:containerDetail.next-restart— “Next Restart:”deployments:containerDetail.path— “Path”deployments:containerDetail.port— “Port”deployments:containerDetail.processing— “Processing…”deployments:containerDetail.refresh-logs— “Refresh Logs”deployments:containerDetail.refresh-status— “Refresh Status”deployments:containerDetail.remove— “Remove”deployments:containerDetail.restart— “Restart”deployments:containerDetail.restart-count— “Restart Count”deployments:containerDetail.restart-count-2— “Restart Count:”deployments:containerDetail.restarting— “Restarting…”deployments:containerDetail.simulate-a-crash-loop-to— “Simulate a crash loop to test how your application handles repeated failures with exponential backoff.”deployments:containerDetail.simulate-an-out-of-memory— “Simulate an Out of Memory (OOM) kill to test how your application handles memory limits. The container will be killed and automatically restarted.”deployments:containerDetail.simulate-crash-loop— “Simulate Crash Loop”deployments:containerDetail.simulate-oom-kill— “Simulate OOM Kill”deployments:containerDetail.simulate-unhealthy— “Simulate Unhealthy”deployments:containerDetail.status— “Status”deployments:containerDetail.status-2— “Status:”deployments:containerDetail.stop— “Stop”deployments:containerDetail.stop-simulation— “Stop Simulation”deployments:containerDetail.stopping— “Stopping…”deployments:containerDetail.suggestion— “💡 Suggestion:”deployments:containerDetail.the-container-will-stop-running— “? The container will stop running and may affect the deployment status.”deployments:containerDetail.this-container-is-not-managed— “This container is not managed by Odysseus. Actions like restart, stop, exec, and simulations are not available. You can still view logs and container details.”deployments:containerDetail.this-will-briefly-interrupt-the— “? This will briefly interrupt the container’s service.”deployments:containerDetail.timeout— “Timeout”deployments:containerDetail.type— “Type”deployments:containerDetail.use-these-buttons-to-test— “Use these buttons to test health check recovery. After”deployments:containerDetail.view-logs-to-diagnose— “View Logs to Diagnose”deployments:containerDetail.view-only-mode— “View Only Mode”
/containers/:id/exec (ContainerExec)
Section titled “/containers/:id/exec (ContainerExec)”deployments:containerExec.back-to-container— “← Back to Container”deployments:containerExec.click-connect-to-start-a— “Click "Connect" to start a terminal session”deployments:containerExec.close— “Close”deployments:containerExec.command— “Command:”deployments:containerExec.connect— “Connect”deployments:containerExec.container-exec— “Container Exec:”deployments:containerExec.container-is-not-running-exec— “Container is not running. Exec is only available for running containers.”deployments:containerExec.deployment— “Deployment:”deployments:containerExec.disconnect— “Disconnect”deployments:containerExec.loading-container— “Loading container…”deployments:containerExec.press-ctrl-c-to-cancel— “Press Ctrl+C to cancel commands. Use Ctrl+D or type "exit" to close the shell. The terminal supports interactive programs like vim, top, and htop.”deployments:containerExec.status— “| Status:”deployments:containerExec.tips— “Tips:”
/containers/:id/logs (ContainerLogs)
Section titled “/containers/:id/logs (ContainerLogs)”deployments:containerLogs.all— “All”deployments:containerLogs.back-to-container— “← Back to Container”deployments:containerLogs.clear-search— “Clear search”deployments:containerLogs.container-logs— “Container Logs:”deployments:containerLogs.container-replaced— “Container replaced”deployments:containerLogs.container-replaced-explain— “This container no longer exists — it was replaced, most likely by an upgrade of its deployment. Streaming from the old container has stopped because it cannot succeed.”deployments:containerLogs.debug— “Debug”deployments:containerLogs.deployment— “Deployment:”deployments:containerLogs.error— “Error”deployments:containerLogs.info— “Info”deployments:containerLogs.level— “Level:”deployments:containerLogs.live-stream— “Live Stream”deployments:containerLogs.loading— “Loading…”deployments:containerLogs.loading-logs— “Loading logs…”deployments:containerLogs.no-logs-available— “No logs available”deployments:containerLogs.no-logs-matching-filter— “No logs matching filter "”deployments:containerLogs.no-logs-matching-search— “No logs matching search "”deployments:containerLogs.reattach-searching— “Looking for the deployment’s current container…”deployments:containerLogs.refresh— “Refresh”deployments:containerLogs.scroll-to-bottom— “Scroll to Bottom”deployments:containerLogs.search— “Search:”deployments:containerLogs.search-logs— “Search logs…”deployments:containerLogs.simulate-disconnect— “Simulate Disconnect”deployments:containerLogs.status— “| Status:”deployments:containerLogs.the-stream-will-automatically-attempt— “The stream will automatically attempt to reconnect. You can also manually refresh logs while waiting.”deployments:containerLogs.tip— “Tip:”deployments:containerLogs.warning— “Warning”
What You Can Do
Section titled “What You Can Do”/containers
Section titled “/containers”This screen’s component declares no permission-gated controls.
/containers/:id
Section titled “/containers/:id”This screen’s component declares no permission-gated controls.
/containers/:id/exec
Section titled “/containers/:id/exec”This screen’s component declares no permission-gated controls.
/containers/:id/logs
Section titled “/containers/:id/logs”This screen’s component declares no permission-gated controls.
Where To Go Next
Section titled “Where To Go Next”For what a container actually is relative to the deployment that owns it, see deployments and containers. If a container is restarting instead of settling, work through a container starts, stops and starts again.