Reframe Kusto emulator docs around OCI (multi-client)#2912
Reframe Kusto emulator docs around OCI (multi-client)#2912MrStarktastic wants to merge 1 commit into
Conversation
The published kustainer-linux image is a standard OCI image, so it runs under any OCI-compatible engine (Docker, Podman, and others). These docs previously described it as a "Docker" image and required the Docker client, implying a single-vendor dependency. Minimal reframe (no command changes): - Relabel "Linux Docker container image" as "Linux OCI container image" and name Docker/Podman as example engines (overview + install). - Prerequisites: require "an OCI-compatible container engine, such as Docker or Podman" instead of the Docker client specifically. - Add a note that the docker-based steps work with Podman by swapping `docker` for `podman`; generalize the first-run pull note. The Docker walkthrough is intentionally kept as the concrete example. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f2064c2-d734-4d90-afd5-fa1b1743ff2f
|
@MrStarktastic : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@MrStarktastic : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit c9a340d: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @spelluru |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @spelluru |
Summary
Reframe the Kusto emulator documentation around the OCI image format so it no longer implies a single-vendor (Docker) dependency. The published
kustainer-linuximage is a standard OCI image and already runs under any OCI-compatible engine (Docker, Podman, and others); these docs described it as a "Docker" image and required the Docker client specifically.This is a minimal reframe with no command changes — the Docker walkthrough is intentionally kept as the concrete example.
Changes
kusto-emulator-overview.mdkusto-emulator-install.mddocker-based steps work with Podman by swappingdockerforpodman.docker run/docker ps/docker stopexamples unchanged.Context
Motivated by Docker Desktop licensing friction for customers running the emulator. The team's direction (per Vincent-Philippe Lauzon,
ms.revieweron these articles) is to standardize the docs on the OCI format and present a "multi-client" approach rather than switch to a specific alternative client.Notes for doc writers
-munder rootless cgroups v2) are intentionally left out to keep this change minimal; happy to add a short "Notes for Podman" section if you'd prefer.