Manage Docker containers and Compose apps in Flame IDE. Inspect resource use, read logs, and open container shells alongside your source and project tools.
Docker & Compose in Flame IDE. Select the image to enlarge.
WHY IT HELPS
Keep the next decision in context.
A backend rarely runs alone. Your API, database, cache, and worker can each have their own container and failure mode. Flame brings container inspection and Compose management into the workspace, so you can move from a failing service to its code without reconstructing the context in another app.
See the service behind the process
Browse containers and Compose apps, inspect their state, and keep the runtime view close to the repository you are changing.
Read output before changing code
Use container logs and a shell to inspect a failing service. Pair that evidence with Flame's terminal, API client, and database tools when a problem crosses service boundaries.
Understand resource pressure
Inspect real-time CPU and memory charts for running containers. Check whether the service is busy or restarting before deciding where to investigate.
HOW TO USE IT
A practical starting point.
Prepare the local Docker runtime
Install and start Docker, make its CLI available to the host running Flame, and verify that your account can access the Docker daemon. Keep the project's Dockerfile and Compose configuration in the repository.
Open Containers
Select the project and open Containers from the activity bar. Inspect the loaded containers and Compose apps, then open the service that belongs to your task. Review the target before starting or stopping anything.
Trace the failure
Read the container's logs and inspect CPU and memory. Open a shell when you need to inspect the container environment, then return to the source, API request, or database query related to the error.
Make the launch repeatable
Use a Run Configuration for your team's launch commands, such as starting a Compose stack alongside a local frontend. Add stop actions only when that cleanup matches your intended session lifecycle.
REQUIREMENTS & LIMITS
Know what the tool depends on.
Docker and the Compose tooling run on your development host; Flame does not include or replace the Docker daemon.
Container shells and lifecycle actions operate on the selected Docker resources. Check the container, project, ports, and volumes before making changes.
This workspace manages containers. It does not promise that every IDE tool or extension executes inside a development container.
FAQ
Docker & Compose: common questions
Yes. Flame uses the host's Docker tooling and daemon. Docker must be running and accessible to the account running the IDE.
Use Run Configurations to organize shell commands, package scripts, browser tabs, and other supported actions. Your Compose files remain the source of truth for the container topology.
The terminal remains available. The Containers workspace adds an inspectable view of containers, Compose apps, resource charts, logs, and shell sessions beside your code.