convox start cannot push to registry on macos 14

[dotnich-io]

With a correctly-configured (I believe) development rack on arm64 macos, I am unable to stand up an application on that local rack.

tl;dr error message:

<... snip happy building noises ...>
build  | #19 ERROR: failed to push registry.andy.macdev.convox.cloud/notion-domain:web.BUIHOOSZEET: failed to do request: Head "https://registry.andy.macdev.convox.cloud/v2/notion-domain/blobs/sha256:4638dd7181c7b9ed00f93fc997d92f1ebe9c8dba5d6a7bac56be994c48045da6": dial tcp 127.0.0.1:443: connect: connection refused
build  | ------
build  |  > exporting to image:
build  | ------
build  | error: failed to solve: failed to push registry.andy.macdev.convox.cloud/notion-domain:web.BUIHOOSZEET: failed to do request: Head "https://registry.andy.macdev.convox.cloud/v2/notion-domain/blobs/sha256:4638dd7181c7b9ed00f93fc997d92f1ebe9c8dba5d6a7bac56be994c48045da6": dial tcp 127.0.0.1:443: connect: connection refused

Setup

• Example app
• M1 macbook pro running macos Sonoma (14.2.1)
• Convox CLI version: 3.15.2
• minikube tunnel running and authenticated

Convox development rack:

❯ convox rack 
Name      andy
Provider  local
Router    router.andy.macdev.convox.cloud
Status    running
Version   3.13.0-arm64

(see #743 for reason I'm running a 3.13.0 rack)

Kubectl pod statuses:

NAMESPACE       NAME                                        READY   STATUS      RESTARTS      AGE
andy-system     api-76bddb8bb5-jmp86                        1/1     Running     0             10m
andy-system     atom-7fbd4b9bb-j75nw                        1/1     Running     0             10m
andy-system     registry-8558d7bb6c-5r44l                   1/1     Running     0             10m
andy-system     resolver-5f985fc6cd-kjlhc                   1/1     Running     0             10m
cert-manager    cert-manager-645b4d4bcb-llldz               1/1     Running     0             9m14s
cert-manager    cert-manager-cainjector-57967fcd59-pmnsm    1/1     Running     0             9m14s
cert-manager    cert-manager-webhook-68b8f57ccb-9pfgf       1/1     Running     0             9m14s
ingress-nginx   ingress-nginx-admission-create-grt48        0/1     Completed   0             20m
ingress-nginx   ingress-nginx-admission-patch-z6lh5         0/1     Completed   0             20m
ingress-nginx   ingress-nginx-controller-6c55c66679-b9dk4   1/1     Running     0             20m
kube-system     coredns-64897985d-kv2nj                     1/1     Running     0             20m
kube-system     etcd-minikube                               1/1     Running     0             20m
kube-system     kube-apiserver-minikube                     1/1     Running     0             20m
kube-system     kube-controller-manager-minikube            1/1     Running     0             20m
kube-system     kube-ingress-dns-minikube                   1/1     Running     0             18m
kube-system     kube-proxy-s5s8r                            1/1     Running     0             20m
kube-system     kube-scheduler-minikube                     1/1     Running     0             20m
kube-system     storage-provisioner                         1/1     Running     2 (20m ago)   20m

[dotnich-io]

Confirming this behaviour is still present in 3.16.0 after standing up a development rack based off #748.