Images
Pull, build, push, analyze, and scan Docker images.
Pull, build, push, analyze, and scan images from this page. Browse Docker Hub from the same place.
Image list
Sort by size or created time, and switch between all images and dangling images when cleaning up old layers.
All images include every tag available locally. Use this view to inspect, retag, build from, push, or scan an image.
Dangling images are untagged layers left behind by builds. Use this view to delete unused intermediates.
Pull an image
Dockerman suggests registries, image names, and tags as you type in the pull combobox. Added in v4.7.0.
Open the Pull dialog
Click Pull from the Images page.
Enter the image reference
Type the registry, repository, and tag you want to pull.
Watch the streaming progress
Follow the layer download and extract progress until the image appears in the list.
Browse Docker Hub
Added in v4.6.0.
Use the Hub browser to search, inspect, and pull public images.
Open the Hub browser
From the Images page, click Browse Docker Hub.
Search for an image
Type a query, then review the official and verified badges in the results.
Read the README and tags
Click an image to view its README inline and the full tag list.
Pull a specific tag
Click Pull next to the tag you want to use.
Build from a Dockerfile
Build uses the same Docker daemon as the rest of Dockerman, and BuildKit is used automatically when the daemon supports it.
Choose a build context
Select a local folder that contains the Dockerfile.
Review or edit the Dockerfile
Open the Dockerfile in Monaco, then save your changes to disk before you build.
Set the image name and build args
Set the image tag, optional build arguments, and a target stage if you need one.
Run the build
Watch the build logs stream in the terminal until the image appears in the Images list.
Dockerman honors .dockerignore in the selected build context.
Push to a registry
Added in v4.6.0.
Push a tagged image after selecting a registry configured in Dockerman's registry manager.
Tag the image for the target registry
Use a full name like registry.example.com/team/app:1.2.0.
Configure registry credentials
Add or select a registry in the registry manager. The push dialog requests credentials from that saved entry; it does not promise to import ~/.docker/config.json or accept ad-hoc credentials per push.
Push with streaming progress
Follow the upload progress until the registry accepts the new tag.
Public and private registries both work here, including Docker Hub, GHCR, Harbor, AWS ECR, Nexus, and GitLab Container Registry.
Analyze image size
Open the Image Size view to see the layer tree and where the image spends its space. Watch for:
- Oversized package caches left in the final layer
- Build artifacts that belong in a smaller runtime image
- Redundant
COPYlayers that duplicate the same files
Tag operations
Use tag operations to tag, untag, or retag an image for another repository or registry. Retagging changes the reference only; the underlying layers stay where they are.
Scan with Trivy
Added in v4.6.0.
Scan an image for known vulnerabilities in its installed layers.
First-time install
If the managed Trivy binary is missing, Dockerman prompts you to install it. Trivy may then download or update its vulnerability database during a scan.
Network access may be required for both binary installation and database updates. Cache state and download size depend on the installed Trivy version.
Run a scan
Select an image
Pick the image you want to scan from the Images page.
Click Scan with Trivy
Dockerman starts the scan and streams progress into the report view.
Wait for the report
Typical scans take 30 seconds to 3 minutes, depending on image size.
Read the report
Dockerman groups findings by severity. Expand each finding for the CVE ID, description, affected versions, and fix versions when available. Export the raw report as JSON to feed into CI or archive the result.
Cleanup
- Remove dangling images from the Dangling tab to clear build leftovers.
- Delete old versions with multi-select when you no longer need a tag.
- Use Prune on the Images page to ask the selected runtime to remove unused images.