iamasmith
iamasmith
Of course!, I'm always wary of just doing that our Gitlab instance at work is finicky about merge commits entering branches and rejects anything on the branch at push time...
Take your time and review, I'm happy with the version with these changes on my home lab so probably won't check back so much but if you want any changes...
@pl4nty it's not at the moment, it's only in my home lab repo. I'll see if I can push it up to ghcr soon if you like, it's currently built...
I'll have to spend some time working out what PAT permissions to use. I'm not using Github actions, my build runners run off Gitlab.
@pl4nty I've built the arm64 image as well as amd64 now, pushed them both up and joined them into a multi-arch image at ghcr.io/iamasmith/external-mdns - both archs seem to run...
Apologies for the delay, the Mrs wanted to go out for a walk first. I decided against running ARC and using Gitlab Actions when I found that it wouldn't work...
just checking in @pl4nty to see how you are getting on..?
On GKE any duplicate layer included makes the image incompatible with image streaming until adopting 1.28 https://cloud.google.com/kubernetes-engine/docs/how-to/image-streaming
Reported on the 19th April there appears to be an additional issue noted with Image Streaming that again appears to be triggered under certain circumstances by duplicate layers.
wrt PTR records? no, as I mentioned I didn’t tackle that one directly so it’s no worse than before but could probably be improved upon. The change would require something...