Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Build drivers table and OCI/Docker exporter page say the docker driver can't export tarballs or multi-platform images

Open Beginner friendly
  • Is something wrong?
#26,372 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, markdown
Domain
documentation

Research direction

Start by locating the Build drivers table and the OCI and Docker exporters page in the Docker documentation. Check the surrounding wording and linked multi-platform-build guidance, then update both pages so support is described for the docker driver with the containerd image store while preserving the classic-worker restriction. Done means the pages no longer contradict the documented behavior and accurately cover both storage modes.

Written by the indexing model from the issue text.

Description

Two pages say that the default docker driver can't do something it can do with the containerd image store:

  • Build drivers: the table leaves Tarball output and Multi-arch images empty for docker.
  • OCI and Docker exporters: "The docker driver doesn't support these exporters. You must use docker-container or some other driver."

With the containerd image store, which is the default for Docker Desktop and for fresh Docker Engine 29.0+ installations (containerd image store), both work with the docker driver. Multi-platform builds already says that no extra setup is needed in that case, so the pages disagree.

What I ran

Docker Desktop, Engine 29.7.2, buildx v0.36.1, containerd image store, builder desktop-linux (driver docker), FROM scratch + one COPY:

$ docker buildx build --builder desktop-linux --output type=oci,dest=out-oci.tar .        # exit 0, tar has index.json, oci-layout
$ docker buildx build --builder desktop-linux --output type=docker,dest=out-docker.tar .  # exit 0, tar has index.json, manifest.json, oci-layout
$ docker buildx build --builder desktop-linux --platform linux/amd64,linux/arm64 \
    --output type=oci,dest=out-multi.tar .                                              # exit 0, index.json has an image index

In moby, daemon/internal/builder-next/worker/containerdworker.go passes every exporter except moby to the BuildKit containerd worker, which has the oci and docker exporters. The classic worker (worker/worker.go) only has moby, local and tar, so the current text is still right for the classic storage drivers.

I didn't run a build on Docker Engine on Linux.

I can open a PR that marks these cells as supported with the containerd image store and updates the exporter page.

This report was prepared with the help of an AI assistant (Claude); I reviewed and verified it.

🤖 Generated with Claude Code

Dominant language
Markdown
Stars
4.7k
Forks
8.5k
Avg merge
2d 5h
Merged PRs (30d)
145

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/docs

All issues in docker/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.