In this "minimal" sub-directory, pull the container images.
```
docker compose pull
```
Run the project.
```
docker compose up --detach
```
Modify the state in ./persistent/, and bounce the container.
```
docker compose up --force-recreate --detach
```

Observe the logs

docker compose logs quickstart --follow

Run the CLI inside the quickstart environment.

docker compose exec quickstart ziti edge list identities

╭────────────┬───────────────────┬─────────┬────────────┬─────────────╮
│ ID         │ NAME              │ TYPE    │ ATTRIBUTES │ AUTH-POLICY │
├────────────┼───────────────────┼─────────┼────────────┼─────────────┤
│ ZS1YAo4Gnj │ quickstart-router │ Router  │            │ Default     │
│ cOmDAo4Gb  │ Default Admin     │ Default │            │ Default     │
╰────────────┴───────────────────┴─────────┴────────────┴─────────────╯
results: 1-2 of 2

Develop Ziti

This replaces the ziti binary that's running the quickstart.

In the top-level directory of the ziti project, build the binary.
```
go build -o ./build ./...
```
The build command can also be run from this "minimal" sub-directory.
```
go build -o ../../../build ../../../...
```
In the "minimal" sub-directory, with Dockerfile present:
```
docker compose up --detach --build
```

Troubleshooting

Changing File Locations

The Compose project file compose.yml and Dockerfile have file paths that represent the assumption they're placed in a sub-directory three levels deep in a checked-out copy of the openziti/ziti source repository. This allows the Dockerfile to copy the built binary from the top-level directory ./build. You can move these files outside the source tree if you adjust the paths in both files.

Building `ziti` in the Dockerfile

If the binary you build on your host doesn't run in the container due to an environment issue, such as a GLIBC version mismatch, you have the option to build ziti in the container every time you run up --build.

Change Dockerfile like this, and run docker compose up --detach --build to build the checked-out source tree and run the quickstart with the build.

FROM golang:1.20-bookworm AS builder
WORKDIR /app
COPY go.mod go.sum ./
RUN go mod download
COPY . .
RUN go build -o ./build/ ./...

FROM debian:bookworm-slim
COPY --from=builder /app/build/ziti /usr/local/bin/

CMD ["ziti"]

Gotcha - Clobbering the Container Image

With docker compose up --build, the container image specified in image is replaced with the one built from the Dockerfile. This clobbers any image you may have pulled from the registry unless you change the value of image or comment the line.

    # commenting "image" avoids clobbering the image pulled from the registry
    # image: ${ZITI_QUICK_IMAGE:-docker.io/openziti/ziti-cli}:${ZITI_QUICK_TAG:-latest}
    build:
      context: ${ZITI_SRC_ROOT:-../../../} 
      dockerfile: ./quickstart/docker/minimal/Dockerfile

Next time you run docker compose pull the image from the registry will be refreshed in the local cache.

README.md

minimal Docker quickstart

Run Ziti

Develop Ziti

Troubleshooting

Changing File Locations

Building ziti in the Dockerfile

Gotcha - Clobbering the Container Image

Building `ziti` in the Dockerfile