Local exporter: Export individual files

Open
#874 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
build-system, cli

Research direction

Start by tracing the buildctl local exporter and the client library's State and ExecState APIs, including the mentioned AddMount limitation. Determine how an individual part of an output filesystem should be selected and exported, then define tests covering the intended export behavior.

Written by the indexing model from the issue text.

Description

help wanted kind/enhancement

Is there a way to export only parts of the output filesystem to local filesystem?

I haven't found a buildctl option to do that.

I guess I could theoretically define a graph that ends with a scratch state and mounts parts of another state. However, the client library doesn't seem to provide AddMount for State, but only for ExecState, and I don't see a trivial way to form the latter from the former. In any case, such an additional mounting step would seem like an avoidable inconvenience to me...

Dominant language
Go
Stars
10.3k
Forks
1.5k
Avg merge
1d 23h
Merged PRs (30d)
48

Contributor guide

Open the contributing guide

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 moby/buildkit

All issues in moby/buildkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.