Portable Gunbot Container
Check out our ready-to-build Docker container that comes with Gunbot preconfigured for first-time setup. It’s designed for quick deployment — no manual configuration required. The container includes built-in OpenSSL certificate generation, automatic data persistence management, and a fully integrated environment that’s ready to set up and run right out of the box — whether you’re deploying locally or on a server.
A Secure, Reliable Foundation Out of the Box
Everything is wired up before you start: SSL, persistence, and a running Gunbot GUI — no manual configuration required.
Fully Standalone Image
The container is fully standalone and portable. It requires no GitHub or Docker Hub during runtime — you only need Docker installed on the host.
Auto OpenSSL Certificates
On first run, self-signed SSL certificates are generated automatically so Gunbot serves over HTTPS by default on port 5000.
Persistent Data Management
All configs, logs, SSL certs and binaries are stored in the host’s ./GB folder so your Gunbot state survives restarts — back up or move that folder to keep it.
Deploy the Container in 7 Steps
Prepare folders, load the tar image, run with persistence, then open the GUI. Stop / start / remove anytime.
Prepare folders on the host
Create a folder for the tar file (example):
Example: D:\docker-apps\
Create a folder for persistent Gunbot data (the container will populate this on first run):
Linux: mkdir -p ./GB Windows (PowerShell): mkdir .\GB
Put the container tar file in your tar folder
Copy gunbot-standalone.tar into the folder where you’ll run the next command (the same folder you created above).
Load the container image
Run this from the same location as gunbot-standalone.tar:
docker load -i gunbot-standalone.tar
Run the container with persistence
Run the container (this mounts the host ./GB into the container at /home/GB):
docker run -d -p 5000:5000 -v ./GB:/home/GB --name gunbot gunbot-standalone
What happens on first run:
- ✓ Gunbot files are copied into
./GBif that folder is empty. - ✓
config.jsis patched toport: 5000andhttps: true. - ✓ OpenSSL certificates are generated automatically (self-signed by default).
- ✓ All configs, logs and binaries are persisted in
./GBon the host so they survive restarts.
Access the Gunbot GUI
Because the container enables HTTPS by default, open your browser to:
https://localhost:5000
You may see a browser warning about a self-signed certificate — that is expected for the default self-signed cert. Accept the warning to proceed (or install the generated cert into your system/browser if you want to remove the warning).
Stop / start / remove the container
docker stop gunbot docker start gunbot docker rm -f gunbot
Useful for troubleshooting:
docker ps -a # show container status docker logs -f gunbot # stream container logs
Notes & Portability
A few things worth remembering before you deploy, move, or back up your container.
Standalone & Portable
- runtime depsDocker onlyThis container is fully standalone and portable — it requires no GitHub or Docker Hub during runtime. You only need Docker installed on the host.
- state locationhost ./GBAll persistent files (configs, logs, SSL certs, binaries) are downloaded and stored in the host ./GB folder. Back up or move that folder to keep your Gunbot state.
Bind a Specific Host Path
- WindowsD:\docker-apps\GBIf you want the container to bind to a specific host directory path (absolute), replace ./GB with the absolute path.
- Linux/srv/gunbot/GBSame idea on Linux — swap ./GB for your chosen absolute mount point in the docker run command.
HTTPS & Certificates
- protocolhttpsThe container enables HTTPS by default (config.js is patched to https: true on first run).
- certsself-signedSelf-signed certs are auto-generated. A browser warning is expected; install the generated cert to remove it.
Files
The container tar file and its SHA256 checksum so you can verify integrity before loading.
Ready to Deploy Your Gunbot Stack?
Grab the container, run it in two commands, and have a secure, persistent Gunbot GUI up on port 5000 — no manual configuration required.