This issue is focused on implementing a local API for artifact creation.

[3129097127] Upstream Reporter: Daniel J Walsh
Upstream issue status: Open
Upstream description:

Feature request description

Currently when doing a build on a local system like MAC or Windows, users often already have the home directory mounted into the VM. When we do a podman artifact add or a podman build, the artifact or context directory is added to a tar ball and sent to the remote service, where it is untarred and processed. Most of the time this is an unnecessary step since the file or context directory is already available in the VM via the overlayfs file system.

Suggest potential solution

Adding a libpod api to do a local artifact add or build context, would allow podman-remote to optimize these steps and should speed up the process.

Podman remote then could either figure out if the local file/context directory is available in the VM or fail over the the remote API when the local API fails.

Have you considered any alternatives?

Going with the current method works, but this is an optimization.

Additional context

This would give us a serious speed advantage to Docker.

Upstream URL: https://github.com/containers/podman/issues/26321