wide-mechanic-33355
09/11/2023, 7:02 AMK3S_RESOLV_CONF
or --resolv-conf
or /etc/rancher/k3s/config.yaml
but I can't seem to find out where to configure those options when using rancher-desktop on an M1 Mac. It also doesn't seem to be using my local /etc/resolv.conf file either.
I'm using coredns and I've tried using autopath but that also doesn't seem to work. I know I can manually edit the deployment files to add the dns search domain, but I've got A LOT of deployments to work with and updating each one individually is going to take forever to complete.proud-agent-52802
09/11/2023, 12:01 PMproud-easter-69184
09/11/2023, 2:14 PMFROM busybox
ONBUILD RUN exit 1
Lets say we call this ‘baseimage’ and build and push.
Then in my next dockerfile I’ve been trying
FROM baseimage:versionAbove
RUN *some stuff*
I would expect the second build to fail but it doesn’t seem to be. I’m happy to accept it could be something I’m doing wrong here 😂dry-article-94077
09/11/2023, 5:26 PMmany-kilobyte-89958
09/12/2023, 7:35 AMfast-oil-88387
09/12/2023, 7:39 AMfew-sundown-80544
09/12/2023, 11:15 AMfast-garage-66093
09/12/2023, 7:23 PMfast-garage-66093
09/12/2023, 7:24 PMflaky-laptop-40437
09/13/2023, 1:26 PMvolumeMounts:
- mountPath: /var/run/docker.sock
name: socket
env:
- name: DOCKER_HOST
value: "/run/k3s/containerd/containerd.sock"
- name: TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE
value: "/var/run/docker.sock"
volumes:
- name: socket
hostPath:
path: /run/k3s/containerd/containerd.sock
Any help will be great, thanks in advance!quick-greece-82875
09/13/2023, 2:16 PM2023-09-13T14:13:27.519Z: Error fetching services: TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
what's even more weird is that k3s is running and I can access it, but rancher desktop seems to think that it isn't...
any idea ?quick-greece-82875
09/13/2023, 2:17 PMrefined-scooter-91545
09/13/2023, 4:51 PMrefined-scooter-91545
09/13/2023, 5:35 PMbland-ocean-59966
09/13/2023, 6:58 PMbland-ocean-59966
09/13/2023, 7:00 PMsome-florist-16358
09/14/2023, 1:30 AMnarrow-pencil-35510
09/18/2023, 7:06 AMnarrow-pencil-35510
09/18/2023, 7:08 AMcareful-country-55345
09/18/2023, 12:29 PMcareful-country-55345
09/18/2023, 12:30 PMcareful-country-55345
09/18/2023, 12:32 PM2023-09-18T12:19:51.616Z: mainEvents settings-update: {"version":9,"application":{"adminAccess":true,"debug":false,"extensions":{"allowed":{"enabled":false,"list":[]},"installed":{}},"pathManagementStrategy":"rcfiles","telemetry":{"enabled":true},"updater":{"enabled":true},"autoStart":true,"startInBackground":true,"hideNotificationIcon":false,"window":{"quitOnClose":false}},"containerEngine":{"allowedImages":{"enabled":false,"patterns":[]},"name":"moby"},"virtualMachine":{"memoryInGB":4,"numberCPUs":2,"hostResolver":true},"WSL":{"integrations":{}},"kubernetes":{"version":"1.17.17","port":6443,"enabled":true,"options":{"traefik":true,"flannel":true},"ingress":{"localhostOnly":false}},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"<http://k8s.io|k8s.io>"},"diagnostics":{"showMuted":true,"mutedChecks":{}},"experimental":{"virtualMachine":{"type":"qemu","useRosetta":false,"socketVMNet":false,"mount":{"type":"reverse-sshfs","9p":{"securityModel":"none","protocolVersion":"9p2000.L","msizeInKib":128,"cacheMode":"mmap"}},"networkingTunnel":false,"proxy":{"enabled":false,"address":"","password":"","port":3128,"username":"","noproxy":["0.0.0.0/8","10.0.0.0/8","127.0.0.0/8","169.254.0.0/16","172.16.0.0/12","192.168.0.0/16","224.0.0.0/4","240.0.0.0/4"]}}}}
2023-09-18T12:19:54.777Z: Kubernetes was unable to start: Error: spawn /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura> EACCES
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -13,
code: 'EACCES',
syscall: 'spawn /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura>',
path: '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura>',
spawnargs: [
'shell',
'--workdir=.',
'0',
'chmod',
'644',
'/tmp/rd-nginx.conf-yFu3pK.nginx.conf'
]
}
careful-country-55345
09/18/2023, 12:33 PMbored-farmer-36655
09/18/2023, 1:06 PMcareful-country-55345
09/18/2023, 1:44 PMwitty-motorcycle-1096
09/19/2023, 10:26 AMwitty-motorcycle-1096
09/19/2023, 10:29 AMagreeable-tailor-88876
09/19/2023, 10:40 AMstaff:tim
, but on the container side is games:501
. A coworker found a workaround using colima directly like this:
colima start --arch aarch64 --vm-type=vz --vz-rosetta
but he couldn’t find an equivalent option with Rancher Desktop. Thoughts?modern-tent-35214
09/20/2023, 6:37 AMbulky-byte-66090
09/20/2023, 8:21 AM