Create containers your way
Use quick setup, or go advanced with ports, volumes, networks, environment variables, CPU and memory limits, and custom mounts.
A powerful VSCode extension designed to help you manage Podman containers, images, volumes, networks, and pods directly from your development environment.
One tree view for every resource, with the actions you reach for most one click away.
Use quick setup, or go advanced with ports, volumes, networks, environment variables, CPU and memory limits, and custom mounts.
Read container logs in the Output panel or a dedicated terminal. Open an interactive shell or run a command in any container.
Up, down, start, stop and restart services with Docker Compose or Podman Compose, including remote compose. Project names are detected and compose file locations are remembered.
Build from a Dockerfile, push to a registry (opt-in, with an optional default registry), and clear out what you no longer need.
Create pods with a name, hostname, extra hosts and CPU shares. Start, stop, restart, or add a stopped container to one.
One button in the title bar starts or stops your machine and shows its state, and the status bar reports it at startup. Using a named machine? Set it once in settings.
Create them, inspect their details, and remove them. Deletes are forced, so a stuck resource doesn't get in your way.
View details opens the podman inspect output for containers, images, volumes, networks and pods. Every action is both an inline icon and a right-click entry.
Podman and compose run with an argument list, never through a shell. The path and machine settings can only be set in your user settings, and untrusted workspaces are restricted.
Find any action from the Command Palette, or filter the full list here.
podman inspect output of any resourcePodmanager is built in the open. Report a bug, request a feature, or send a pull request.
git clone https://github.com/dreamcatcher45/podmanager.gitYes. Podmanager drives your local Podman, so it needs to be installed and reachable from your command line. If it lives somewhere unusual, set podmanager.podmanPath.
Yes. It supports docker-compose.yml and docker-compose.yaml, with up, down, start, stop and restart. Pick the command style that matches your setup with podmanager.composeCommandStyle, and register compose files by project folder so they are remembered.
Deletes are confirmed with a prompt, and you can turn that prompt off with podmanager.confirmDeletions. Deletes are force removals.
In the Output panel (a one-time dump) or a dedicated terminal (live, following the log). Switch between them with podmanager.logsOutput.
Yes. It is off by default: enable podmanager.enablePushCommand and set a default registry with podmanager.pushDefaultRegistry to pre-fill the destination.
Podman cannot move a container, so Add Container to Pod re-creates a stopped container inside the pod. The container gets a new ID and the original is replaced.
Yes. podmanager.podmanPath and podmanager.composePath accept a command with arguments, such as flatpak-spawn --host podman, sudo podman or podman --remote. Quote paths that contain spaces.
On purpose. podmanPath, composePath and machineName decide which program runs, so they are machine-scoped and can only be set in your user settings. That stops a repository from running commands the moment you open it.
Not by default. Set podmanager.autoRefreshInterval to a number of seconds (minimum 5) to refresh while the view is visible. 0 turns it off.
Yes. A button in the view title bar starts or stops the machine and shows its state, and the status bar reports it at startup. Set podmanager.machineName if you use a named machine.