Docker.vim

Docker.vim is an archived Vim plugin for terminal-oriented users to manage Docker images and containers, listing resources and providing pull, build, tag,…

  • Infrastructure
  • Other
  • Productivity
  • Tools & Utilities
Docker.vim is an archived Vim plugin for terminal-oriented users to manage Docker images and containers, listing resources and providing pull, build, tag, run, and log actions, with denops-docker.vim as the maintained successor.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

31/100 Low

Maintained
0GitHub repository is archived
Popular
45174 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
75no serious findings

Availability: platform listings confirmed today

GitHub stars
174
Open issues
0
Last commit
2021-07-21
Activity
stale

Checked 9 days ago - source: GitHub (skanehira/docker.vim)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 6 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install Docker, kubectl, and Helm first On macOS, use Homebrew (a macOS installer program) to install Docker, kubectl (a Kubernetes control tool), and Helm (a chart installer) before following the guide. Without these tools, later container commands will fail. source
  • Use compose and keep shared memory mounted Save the supplied docker-compose.yml and run it; it starts the Hub (the coordinator) plus Firefox and Chrome nodes and mounts /dev/shm (temporary shared memory) for the browser containers. Skipping that mount can make browser tests crash. source
  • Set up network, ports, and node connection For the manual path, create a Docker network named grid (the way containers talk to each other) and start the Hub with ports 4442-4444 open (Selenium ports) before the Node. Set SE_EVENT_BUS_HOST=selenium-hub on the Node (the name it uses to find the Hub), or the Node cannot register. source
  • Stopped development The README states that docker.vim development has stopped and the author recommends switching to the successor plugin, denops-docker.vim. source
  • Requirements Requires the Docker CLI on the host PATH and the vim-jp/vital.vim dependency; install with a Vim plugin manager such as vim-plug. source
  • Maintained successor Use denops-docker.vim, the maintained successor recommended by the author. source

Fetched 3 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I configure docker.vim to push images to a registry?

Set g:docker_registry_auth with the username, password, email, and server address. You can also read those auth values from a JSON file.

How do I use tmux when attaching to a container?

Set g:docker_use_tmux to 1 to enable tmux for attaching to a container.

How do I view a container's logs in Vim?

Use :DockerContainerLogs with the container id or name. If the container is not running, the terminal does not close automatically.

Can I run docker.vim from a Docker container?

The README gives an example that mounts the host Docker socket into the container at /var/run/docker.sock. This lets the plugin manage the host Docker daemon.

How do I build an image from the current buffer?

The README shows using DockerImageBuild with -t {tag_name} . for a Dockerfile and -t {tag_name} - to use the buffer contents.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads