<p>I've been able to get two awesome technologies to work independently.</p>

<ul>
<li><a href="https://github.com/GoogleContainerTools/skaffold" rel="nofollow noreferrer">Skaffold</a></li>
<li><a href="https://docs.docker.com/buildx/working-with-buildx/" rel="nofollow noreferrer">BuildX</a></li>
</ul>

<p>Unfortunatly I don't know how to use them both at the same time.</p>

<p>I'm currently building and testing on my laptop (amd), then deploying to a Raspberri Pi 4 (arm64) running Kubernetes.</p>

<p>To get this working I use something like:</p>

<pre><code>docker buildx build --platform linux/amd64,linux/arm64 --tag my-registry/my-image:latest   --push  .
</code></pre>

<p>Before attempting to target an arm I was using skaffold.</p>

<p>Is there any way to continue to target multi-playform whilst also using skaffold to build/deploy?
If not, is there any recommendations for alternatives?</p>

<p>Any advice/help is very appreciated, thank-you.</p>

<p>Found the missing piece. Skaffold has the ability to set a custom command, where I could use <code>buildx</code>.</p>

<p><a href="https://github.com/GoogleContainerTools/skaffold/tree/master/examples/custom" rel="nofollow noreferrer">https://github.com/GoogleContainerTools/skaffold/tree/master/examples/custom</a></p>

<pre><code>build:
  artifacts:
  - image: "foo/bar"
    context: .
    custom:
      buildCommand: ./custom-build.sh
</code></pre>

<p><strong>custom-build.sh</strong></p>

<pre><code>docker buildx build \
  --platform linux/arm64 \
  --tag $IMAGE \
  --push \
  $BUILD_CONTEXT
</code></pre>
