You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be convenient if a buildkit instance could be configured to default to a specific frontend.
The usecase for us is that we have developed a frontend that injects certificates and TLS proxy related environment variables into ExecOps and it would be very helpful if we could configure the buildkit daemon to always use this custom frontend
The text was updated successfully, but these errors were encountered:
An addition to this is that docker build --build-arg=BUILDKIT_SYNTAX=... ... doesnt seem to work with the dockerfile.v0 frontend disabled
This could be added to buildx as a special case I think. buildctl build --frontend=gateway.v0 --opt source=image should work fine with Dockerfile disabled.
An addition to this is that docker build --build-arg=BUILDKIT_SYNTAX=... ... doesnt seem to work with the dockerfile.v0 frontend disabled
This could be added to buildx as a special case I think. buildctl build --frontend=gateway.v0 --opt source=image should work fine with Dockerfile disabled.
Ah ok I will file a FR on the buildx repo for that then
Description
It would be convenient if a buildkit instance could be configured to default to a specific frontend.
The usecase for us is that we have developed a frontend that injects certificates and TLS proxy related environment variables into ExecOps and it would be very helpful if we could configure the buildkit daemon to always use this custom frontend
The text was updated successfully, but these errors were encountered: