DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run Gideon in one Docker container with persistent state with Centra Gideon Agent

Build the single-container image from the checkout and run it with a persistent volume.

Credentials. The container holds your workspace, state and provider credentials on the gideon_home volume, so protect the Docker host and the access URL.

Who it is forAn operator or a Windows user who wants a self-hosted Gideon without installing Python and Node on the host.

The problemInstalling Python, Node and the console build on each machine is slow and fragile, and state can be lost when a container is recreated.

The outcomeA Gideon container listening on localhost port 10000 that keeps workspace and state on a named volume, with the access URL in the logs.

What you need first

  • Python 3.12 or newer
  • Node.js 22.12 or newer with npm, if you build the console from source
  • macOS or Linux, or Docker on Windows
  • A model provider credential or a local model, configured in the console after first start
  • A workspace directory and timezone for gideon setup

Steps

  1. Run docker build -f deploy/docker/Dockerfile.backend --target single -t gideon:local . from the checkout.
  2. Run docker run -d --name gideon --restart unless-stopped -p 127.0.0.1:10000:10000 -v gideon_home:/data gideon:local.
  3. Run docker logs gideon and copy the access URL it prints.
  4. Open the access URL in a browser and add a model provider in the console.

Prompt for your agent

In the Sidiora-Labs/centra-gideon-agent checkout, build the image with the README Docker command and run the container named gideon. Report the access URL from docker logs gideon. Verify that the container is running with docker ps before you report success.

Caveat. The README publishes the port on 127.0.0.1 only, so the console is reachable from the Docker host unless you change that bind address yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page