greptimedb-development-docker-image

GreptimeDB Development Docker Image

Goal

Package a locally built GreptimeDB binary into a development-only Docker image for debugging and local-cluster testing, optionally push it to a development registry, and retain the non-secret image settings in .env for the next build. It is not a release-image workflow and must not be used to publish a production or release artifact.

This skill follows the documented development-image build procedure:

• Build greptime with Cargo's nightly profile.
• Copy the target binary into the Docker build context as ./greptime.
• Build the supplied Dockerfile, which uses Ubuntu 24.04 only as the runtime base image and exposes the greptime binary as its entrypoint.

Inputs

Collect or discover the following before any build or push:

Input	Discovery and rule
Source repository	Treat the directory in which this skill is invoked as the default workspace. Include it as an editable field in the batch configuration; do not ask a separate confirmation. Do not assume open-source versus Enterprise.
Edition and binary	Default to greptime; use the binary name the user requests for Enterprise builds. The copied Docker-context filename must always be greptime.
Cargo profile and binary source	Include this in the batch configuration. Default to rebuilding nightly; reuse an existing binary only after the user explicitly accepts that its freshness is unverified.
Target platform	Preselect linux/amd64 unless Docker's server is linux/arm64, then preselect linux/arm64. Let the user override it in the batch configuration. Ubuntu 24.04 is the runtime base image, not a target-platform choice. Each image has exactly one target platform, but it may differ from the host platform.
Build mode	Ask whether the user wants a locally loadable debug image or a registry push.
Registry/repository	Read IMAGE_REGISTRY and IMAGE_REPOSITORY only from the selected workspace's .env and prefill them in the batch configuration. Example: registry.example.com/team + greptimedb-dev.
Tag	Read IMAGE_TAG only from the selected workspace's .env and prefill it in the batch configuration. When the tag exists in the selected registry, preselect an incremented version.

Use the image reference ${IMAGE_REGISTRY}/${IMAGE_REPOSITORY}:${IMAGE_TAG}. If the registry is intentionally empty, omit its slash rather than producing a leading slash.