Skip to main content
0 reactions

How to Run Valkey Admin in Docker

Featured card titled Run Valkey Admin in Docker, The web version of the official Valkey GUI in your browser, with a container named valkey-admin listening on 8080 inside and an arrow to a browser at localhost:8091.
Run Valkey Admin in Docker.

Valkey® Admin, the Valkey project’s app for working with Valkey in a window, also comes as a web app in a Docker container. You run one command and open it in your browser.

By the end, Valkey Admin runs in Docker on your computer and is connected to your Valkey server.

Note: Every command and screen on this page is real, from Valkey Admin 1.3.0 in Docker Desktop 4.99 on an Apple silicon Mac.

Prerequisites

Step 1: Start Valkey Admin in Docker

In Terminal, run:

TerminalBash
docker run -d --name valkey-admin -p 127.0.0.1:8091:8080 --add-host=host.docker.internal:host-gateway valkey/valkey-admin:latest
  • -d runs it in the background, so you get your Terminal back.
  • --name valkey-admin names the container, so you can stop and start it by name.
  • -p 127.0.0.1:8091:8080 makes the app, which listens on port 8080 inside the container, reachable on port 8091 of your computer, and only from your computer.
  • --add-host=host.docker.internal:host-gateway lets the container reach your computer, and so your Valkey, by the name host.docker.internal.
  • valkey/valkey-admin:latest is the official image on Docker Hub (opens in a new tab).

The first time, Docker downloads the image, then prints the new container’s ID:

Output (the lines that matter)Plain text
Unable to find image 'valkey/valkey-admin:latest' locally
latest: Pulling from valkey/valkey-admin
Digest: sha256:06acd66b82d9cd0dab5d2a5dcc829b6dc18017991b208ba0aa23a378adf1f1af
Status: Downloaded newer image for valkey/valkey-admin:latest
6fd09f933add8d1fea356cf552db64c1ee28eef730c41c031fc08a3da1d93988

Security: Keep 127.0.0.1 in the command. The web version has no sign-in, so anyone who can reach its port can use it, as Valkey Admin’s Docker guide (opens in a new tab) warns.

Step 2: Open Valkey Admin in Your Browser

Go to http://localhost:8091. Valkey Admin opens on its Connections page, empty for now.

Valkey Admin open in a web browser, on the Connections page with the message You Have No Connections and a + Add Connection button.
The web version opens on the same Connections page.

Step 3: Connect It to Your Valkey

Click + Add Connection. Type host.docker.internal as the Host, keep port 6379, untick Use TLS and click Connect. Inside the container, localhost means the container itself, not your computer. How to Connect Valkey Admin to a Valkey Server explains every field.

The Valkey Admin Add Connection form with Endpoint Type Node, Alias Local Valkey, Host host.docker.internal, Port 6379, empty Username and Password, Database 0, Use TLS unticked and a warning that the connection will not be encrypted.
In Docker, the host is host.docker.internal, with Use TLS unticked.

Valkey Admin connects and opens the Dashboard of your server:

The Valkey Admin Dashboard for instance host-docker-internal-6379-db0, with cards showing Total Memory infinity, Used Memory 1.23 MB, Operations 32 and a dash for Hit Ratio.
Connected: the Dashboard of the local Valkey.

If the connection fails with failed to lookup address information: Name or service not known, see Fixed: failed to lookup address information: Name or service not known (Valkey Admin in Docker).

Stop and Start Valkey Admin

Stop the container when you’re done. It keeps its settings:

TerminalBash
docker stop valkey-admin
OutputPlain text
valkey-admin

Start the same container again next time:

TerminalBash
docker start valkey-admin
OutputPlain text
valkey-admin

Common Mistakes

MistakeWhat happensDo this instead
Typing localhost as the HostValkey Admin looks for Valkey inside its own containerType host.docker.internal
Publishing the port without 127.0.0.1Anyone who can reach that port on your computer can use Valkey Admin, which has no sign-in in its web versionKeep -p 127.0.0.1:8091:8080
Leaving out --add-hostOn some setups, connecting to host.docker.internal fails with Name or service not knownAdd the option, as in Step 1. The fix post explains why.

FAQ

Why port 8091 and not 8080?

Valkey Admin listens on 8080 inside its container. The -p option chooses the port on your computer, and 8091 keeps 8080 free for other tools. Any free port works.

How is this different from the desktop app?

The screens are the same, and nothing is installed on your computer except the container. Valkey Admin’s documentation recommends the desktop app for watching hot keys and command logs.

Conclusion

One docker run command starts Valkey Admin at http://localhost:8091. Connect with host.docker.internal, and stop the container when you’re done.

Additional Resources

Valkey® is a registered trademark of LF Projects, LLC. Redis® is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with the Valkey project, LF Projects or Redis Ltd., and isn’t endorsed, supported or certified by them.

0 comments