docker run → Compose and Kubernetes

Why use doconv

• docker run → Compose. Turn a one-liner into ready Compose service YAML.
• Deployment snippet. Also get a starter Kubernetes Deployment — not Helm or kustomize.
• Flag warnings. Options that do not map 1:1 are called out explicitly.
• Browser-only. No API: your command never leaves the device.
• Optional hash share. Copy a URL that carries the docker run in the hash.

How to convert docker run

1. Paste a docker run … command or load an Example.
2. Click Convert — Compose YAML and a Deployment snippet appear.
3. Read the warnings for anything that did not map 1:1.
4. Copy the YAML you need or share a hash link.

Flags, Compose, and Deployment

Not every docker run flag has a direct Compose or Kubernetes twin. doconv is an honest starting point: it maps what it can and warns about the rest — no promise of 100% equivalence.

Tips:

• Always re-check ports, volumes, and networking after conversion.
• --privileged, --network host, and devices often need hand edits.
• -it, -d, and --rm are CLI lifecycle flags and are usually dropped.
• This is not a Helm chart or kustomize generator.
• For YAML edits try yamaster; for resource units try k8size.

What it is for

• drafting compose.yml from a one-line docker run;
• starting a Deployment when moving to a cluster;
• spotting flags that do not map 1:1;
• sharing a command via URL hash;
• teaching the gap between run, Compose, and Kubernetes.

FAQ