go_image + k8s_object on macOS with --cpu k8 about rules_k8s HOT 7 CLOSED

Is the digest different when the image is pushed via docker_push?

It's possible that the digest is different when you publish the image with the Docker client.

If the digest is changing between docker_push and k8s_object it is very likely a bug, and may have to do with cfg = "host" vs. cfg = "target".

from rules_k8s.

container_push gives me c9f1edf07b2e, the expected image!

from rules_k8s.

It's bedtime in Stockholm so I don't have time to try this, but would adding cfg = "host" to the following line do the trick? https://github.com/bazelbuild/rules_k8s/blob/master/k8s/object.bzl#L211

from rules_k8s.

IIUC we want cfg = "target",. "host" is intended for building tools to run on the build machine, e.g. the resolver. "target" is intended for building things for the target environment.

from rules_k8s.

Are you on HEAD, because I think this was fixed.

from rules_k8s.

Ah yes, target was what I meant. And yes, you're right, it's fixed in head and works great. Also, I know you're paid to do this, but all of this code is so much appreciated. :)

from rules_k8s.

LOL, I'm glad! Please don't hesitate to reach out if you have any further problems.

from rules_k8s.