Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--cache-to with remote builders results in the cache being written in the host and not in the remote builder #2980

Open
3 tasks done
GonzaloSaez opened this issue Feb 11, 2025 · 1 comment

Comments

@GonzaloSaez
Copy link

Contributing guidelines

I've found a bug and checked that ...

  • ... the documentation does not mention anything about my problem
  • ... there are no open or closed issues that are related to my problem

Description

When using remote builders together with --cache-to directives, the cache ends up being written into the host filesystem and not the remote builder filesystem.

Expected behaviour

The expected behavior is for the cache layers to be written in the remote builder or at least to have an option to do so.

Actual behaviour

The cache layers are written into the host

Buildx version

v0.19.0

Docker info


Builders list

Using a remote builder

Configuration

dockerfile

Build logs


Additional info

No response

@tonistiigi
Copy link
Member

I guess you mean --cache-to type=local. This is expected, type=local writes cache to your local filesystem on the client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants