![]() ![]() In case anyone else finds this useful, here are details of my setup. So I'm using Wireguard to tunnel between the Linux VM and the Mac, so that the container IPs end up visible on the Mac. The container's IP is not visible to the Mac, just to the Linux VM. Bridged networking there just bridges the containers to the Linux VM. ĭocker Mac runs a Linux VM and then runs your containers on that Linux VM. To access something on I'd then just use. I'd simply use bridged networking in the container which would give the container an IP that works for things running on the Linux host. If I were running Docker on Linux this would not be a problem. If Docker Mac works as well on Apple Silicon I might be able to just stick with that and not need either VMWare or Parallels. Specifically, Wireguard between the Linux VM that Docker Mac creates to run containers and the Mac. That turned out to be not too difficult to deal with by using Wireguard. E.g., if I've got a server that would be foo.com when live on a real server that I'm testing locally in a container, I want it to appear at some_ip:443 on my Mac, not on something like localhost:8443 that Docker maps to port 443 in the container. The only real snag was that I want services running in a Docker container to be reachable from Mac processes on the same port they would be on when deployed on a real server somewhere. I recently have switched to using Docker for that. Most of my use of VMWare Fusion on my Intel Mac is to run Linux VMs. That's assuming that I decide that I actually need such a product. The Ubuntu desktop item looks like it's GNOME.I don't like that Parallels requires a subscription to get more than 8 GB of RAM in a virtual machine so I'll be sticking with VMWare Fusion when I get an Apple Silicon Mac. You can get a desktop: sudo apt install tasksel Canonical could decide to update the ISOs we are downloading. FAQ (or, rather, Frequently Imagined Questions) Could this break in the future? This works, ironically, because Live CD ISOs are not being altered to have newer kernels Canonical is relying on network updates during installation to handle that. "deceptively" meaning it'll be so fast it'll appear it didn't do enough to work. Linux confusion 5.4.0-100-generic #113-Ubuntu SMP Thu Feb 3 18:44: aarch64 aarch64 aarch64 GNU/Linux Use that original one when you next boot, via the boot loader menu. But now you'll have the original one too. Since we disallowed initial installation of a lot of other packages, not just a newer kernel, you will almost certainly need to do the typical apt update and maybe even apt upgrade, if that's how you roll, which will eventually install a newer kernel. The startup will continue and you should land on the login prompt. ![]() Go into the settings and turn the networking adapter back on. The boot sequence will get stuck consulting the network. The install itself will be deceptively quick. Some installation screens will be missing. The cloud-init step will take a while then continue. Disconnect the networking adapter.Ĭontinue with the installation. Make the new VM as usual, EXCEPT say that you want to change the VM settings. The 22H2 release of Tech Preview claims to fix the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |