Reframe Kusto emulator docs around OCI (multi-client)#2912
Open
MrStarktastic wants to merge 1 commit into
Open
Reframe Kusto emulator docs around OCI (multi-client)#2912MrStarktastic wants to merge 1 commit into
MrStarktastic 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
Contributor
|
@MrStarktastic : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
@MrStarktastic : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit c9a340d: ✅ Validation status: passed
For more details, please refer to the build report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.