Images & Tags

Where to pull from

The same image is published to three places. Use whichever you prefer:

Registry	Image
Docker Hub	yeciorg/yeci
Docker Hub (original repository, still updated with every build)	tourcoder/yeci
GitHub Container Registry	ghcr.io/yeciorg/yeci

Tags

Tag	Meaning
latest	The most recent build
YYYYMMDD, for example 20261019	The build from that day. It never changes, so use it to pin an exact set of tool versions.

Every image supports linux/amd64 and linux/arm64; Docker picks the right one for your machine.

The current image is 20261019, updated 2026-10-19. Its contents are listed in Introduction.

Which version am I using?

Inside the container, run:

yeci version

It prints the image's dated tag and architecture, followed by the tool versions the image shipped with:

yeci 20260928 (linux/arm64)
  claude-code 2.1.286   codex 0.159.3   gemini 0.62.0   grok 1.0.46
  swift 6.4.0   node 26.10.0   go 1.27.1   nvim 0.12.5
(versions as shipped in the image; tools that update themselves may now be newer)

Tools that update themselves, such as Claude Code, may be newer than listed. Add --check to also ask Docker Hub whether a newer image has been published (this needs network access):

yeci version --check

On your machine, the same tag is recorded as an image label:

docker inspect "yeci-$PROJECT_NAME" | grep image.version

How updates work

Every day, the tool versions (the AI agents, Node.js, Go, Neovim, yeci-notify) are checked against their latest releases. When anything has changed, a new image is built for both architectures and published with a new dated tag and as latest. When nothing has changed, no new image is published that day.

Updating

yeci version --check tells you whether a newer image is available. To update, pull the new image, then start a new container from it:

docker pull yeciorg/yeci
docker stop "yeci-$PROJECT_NAME"
# then run the docker run command from Quick Start again

A running container keeps using the image it was started from.