tart VS Vagrant

the inability to log in with an Apple ID in a MacOS VM is a decision made by Apple. you can certainly sign without logging in, but I don't think you can submit to the store in a VM.

you can see how they build tart here, including signing and entitlements and so on: https://github.com/cirruslabs/tart/blob/main/.cirrus.yml

Boots in 5 minutes, minimum allocation of 24 hours, is "low stock" if you actually try to allocate one, and was recently "no stock". I'd be unsure if its actually available when you need it.

Would be nice to see a Virtualization.Framework as a service, such as with Tart [1], but perhaps there are performance and security issues when making those M1s multi-tenant. The license limits it to a maximum of two guest systems, and only for the purposes of software development and testing [2].

[1] https://github.com/cirruslabs/tart/

[2] https://www.apple.com/legal/sla/docs/macOSVentura.pdf#page=2 (2B iii)

I haven’t used UTM personally so I can’t vouch for that. There is also Tart.

For a full reproducible solution, I thought of this: https://github.com/cirruslabs/tart

tart, uses also new Virtualization framework and supports ARM Linux on upcoming macOS Ventura

An alternative: https://github.com/cirruslabs/tart

on the off chance one hasn't been tracking it, there were several "we don't need your stinking BuSL" projects when this drama first started:

https://github.com/opentofu#why-opentofu (Terraform)

https://github.com/openbao/openbao#readme (Vault)

and I know of several attempts at Vagrant <https://github.com/hashicorp/vagrant/forks> but I don't believe one of them has caught traction yet

There are also some who have talked about an "open Nomad" but since I don't play in that space I can't speak to it

It sounds like you're using Nix as a sort of configuration management solution. CM just isn't worth it for managing a single desktop IMO. It triples the effort for whenever you need to add or remove a package, as you must now add that also to your nix configuration. You're supposed to be able to make that back up in time saved restoring to the next machine, but inevitably the next machine will be different enough that you'll have to edit it all anyway. In the end I just got tired of trying to manage my own machine with infrastructure as code (though in fairness I was using puppet at the time not nix).

I keep a git repository with all my dot files in it[1]. This seems to work the best. It has a Windows folder as well, and I copy that out whenever I need to set up Windows.

A lot of people like using WSL but I hate how it hogs on my memory. Hyper-V is a terrible virtualization engine for consumer-grade use cases because it can't thin provision RAM. If I need to use docker, I will spin up a small Linux VM using vagrant[3] with Virtualbox[4] and put Docker on there. Vagrant is an extremely underrated tool in my opinion, particularly in a Windows context.

I use scoop for packages. Typically I will scoop install msys2 and then pin it so that it doesn't get blown away by the next upgrade.

Then I basically do all of my development inside of msys2. I can get most things running in there without virtualization. In my case that means sbcl and roswell for common lisp, senpai for irc, and tmux and nvim for sanity. Msys2 uses the pacman package manager and this is good enough.

All In all, I set up my Windows machine affresh after a while of not using it and it took me about 3 hours. Most of that time was just getting through upgrades though, I felt like it was pretty fast.

1: https://git.sr.ht/~skin/dotfiles

2: https://www.msys2.org/

3: https://www.vagrantup.com/

4: https://www.virtualbox.org/

Tools like Docker and Vagrant can be used to allow local environments to mimic production environments.

There's an open issue [1]. A scripting interface has since been added [2], and updated [3], so there's progress.

[1] https://github.com/hashicorp/vagrant/issues/12518

Someone should fork and maintain Vagrant with an MPL open source license:

https://github.com/hashicorp/vagrant

https://github.com/hashicorp/vagrant/blob/v2.3.7/CHANGELOG.m... ?

The changelog lists both improvements and bug fixes and there's even apparently some effort to port it away from ruby: https://github.com/hashicorp/vagrant/blob/v2.3.7/internal/cl...

If you’ve ever encountered the dreaded “Vagrant fatal error: runtime BSDThread_Register error,” you’re not alone. This perplexing error message can be frustrating and confusing, especially if you’re new to Vagrant and virtualization. But fear not! In this article, we’ll unravel the mystery behind this error, explain its meaning, and provide solutions to help you overcome it.

If you want an all around easy to use tool that can manager containers (create on the fly, delete when unnecessary, etc.) look into vagrant. There are also options like xen and virtualbox but they are not so lightweight. All of them are in ubuntu repositories.