John Rofrano

@cdrage Awesome! You might want to tell the Red Hat OpenShift team about this because their docs make no mention of an arm64 version: https://docs.openshift.com/container-platform/4.6/cli_reference/developer_cli_odo/installing-odo.html Thanks for pointing this out....

I'm still seeing this behavior on v2.6.2 but I do have a workaround. Perhaps this will give some insight into what is happening: I added `127.0.0.1 k3d-registry.local` to my `/etc/hosts`...

Hi @bayeslearner, I never noticed that option before. Like you, I cannot find any examples that use it. I will have to play around with it and see what it...

I'm not seeing this behavior. It seems to be working for me. The `Vagrantfile` in my [nyu-devops/lab-flask-rest](https://github.com/nyu-devops/lab-flask-rest/blob/master/Vagrantfile) repo is redirecting commands to `~/.profile` and they are being executed when I...

Confirmed. I'm seeing the same error with the `rofrano/vagrant-provider:ubuntu` image on both Intel and ARM platforms. Apparently they no longer work even when the architectures match! The `rofrano/vagrant-provider:debian` image works...

@rogerbramon Yes, in fact there is something you can do. I've been exploring some options and just need more time to dedicate to this but this is where I'm at....

@ckmorris, @rogerbramon, & @vinalca, I have this working. I upgraded the default `rofrano/vagrant-provider:ubuntu` to be based on `ubuntu:jammy` which is `22.04` and Docker is working again. I worked through the...

Hi @rogerbramon , I am getting the same error for an Intel VM. I forgot that you guys want to run intel VMs on M1. I only use ARM VMs...

@kakoni I was able to reproduce this problem on my M1 Mac mini and I'm looking into it. I couldn't even run `docker hello-world` and I got the same error....

@aamaltf1 Original I use Vagrant with VirtualBox. When Apple came out with its M1 Silicon Macs based on ARM architecture, VirtualBox stopped working because it only supports Intel. Docker runs...