Combine a list of Tart users

[fkorotkov]

As the adoption of Tart is rapidly growing let's create a section of users as a kind of a social proof.

So if you'd like your organization to be highlighted in the upcoming list please comment on this issue and attache a logo that we'll display. Bonus points for a few phrases about your usage/experience.

[testingbot]

We are using it at TestingBot to run automated tests on macOS VMs, running on Mac Mini M1 machines.

Tart was easy to set up and the integrated OCI registry support works great for us 👍

[fkorotkov]

I guess the cat is out of the box and I'm happy to share that Codemagic has migrated from Anka and now uses Tart to power their service as well. Congrats @remarkov and team!

CCing all the people that created issues or commented on one. Please let us know if you started using Tart as well and would like to be highlighted on the main page.

@alexey-tereshenkov-oxb @AllPurposeBen @anjannath @astlock @aw1cks @b00ga @barkingfoodog @ChefAustin @craighurley @cutiechi @damonbreeden @dan-snelson @edude03 @erikng @geerlingguy @jennyli-z @jerrymarino @jmgilman @keisau @keith @kxxoling @Lutzifer @magnusviri @mikehardy @n3rdc4ptn @naikrovek @Nezz @nycnewman @phao5814 @ringods @ryanbooker @saagarjha @sanieldalib @scottslowe @testingbot @TheEagle13 @timsutton @TK5-Tim @torarnv @trodemaster @uurazzle @victor-yousician @vitorgalvao @wegotoeleven

[magnusviri]

I want to switch but I need 2 features. First, external storage. TART_HOME didn't work when trying to put the VM's on external drives. That's to use this on my Mac Mini's. I am running it again right now and I'll create an issue with the error it gives. The other feature is bridged networking. That's to use it on my laptop.

[remarkov]

@fkorotkov thanks a lot, you're doing a great job and Tart is really awesome!

[fkorotkov]

@magnusviri looking forward to your issues/feature requests! Let's make it happen. 😉

@remarkov, me and @edigaryev are very glad! 🙌

[nycnewman]

Thank you for Tart. Recently starting using for self-hosted build pipelines and daily node rebuilds. Looking forward to Apple releasing features to allow automation of the initial image creation. Great work!

[naikrovek]

Looking forward to Apple releasing features to allow automation of the initial image creation.

until then I have a vanilla image that I base everything off of, and I only ever open it to update the OS when updates come out. Everything on top of that vanilla VM is automated, and I only need to update that manually a few times a year. Not too bad at all.

I am kinda surprised that there isn't something like that for MacOS. Something like Windows' autounattend.xml to answer all of that out-of-the-box stuff for you.

[barkingfoodog]

We're using Tart at Suran Systems, Inc. for testing automated server configuration, application installation, and more with Salt Project. Previously we used Test Kitchen + VirtualBox + Vagrant, but that's not an option for current operating systems and Apple Silicon. A Vagrant plug-in would be awesome, but we've been able to build an integration with Cirrus CLI using Test Kitchen that is more than usable. Tart is has been easy to use, dev support has been fantastic, and I love seeing how active the project is. Apple's Virtualization framework is stupid fast and I can't want to move Linux testing over once Ventura ships. Tart solved a critical sticking point in migrating our infrastructure to Apple Silicon and I'm very thankful for the project. Great job everyone!

[nycnewman]

@naikrovek Same situation but would love to automate even this step.

We used to use vagrant + VMWare on Intel, move to packer (base image) + vagrant/VMWare when vagrant broke for build steps and now use packer + tart for daily automation on M1.

[geerlingguy]

I'm working on integrating Tart into the workflow for building, testing, and releasing my macOS Collection for Ansible, as well as my Mac Dev Playbook, used for the automated setup and maintenance of individual Macs. So far I haven't fully settled on Tart for this purpose, but I'm leaning this way.

Getting Tart to work with Vagrant would be a huge boon for me, since that would also allow me to start using it in my workflows for Ansible with Linux and Kubernetes.

[ringods]

I'm in the same camp as @geerlingguy. I want to automate the setup of my Macs. Having a combination of both a Packer and a Vagrant plugin would make it the best replacement for a full testing workflow of this setup using his macOS Collection for Ansible.

If the gap of a Vagrant plugin can be plugged, then I can get rid of the (for macOS) suboptimal hypervisor named VirtualBox.

[aw1cks]

I investigated using Tart to replace bare-metal CI runners, and for that it's quite promising. The thing that stopped me from implementing it is the lack of Intel support, which I understand is an Apple limitation - quite unfortunate. My company has a need for testing against both Intel & Apple silicon for the forseeable future, until Intel Macs are EOL. I'd ideally like to use the same solution for both platforms to reduce the amount of tooling that needs to be learned and maintained.

[naikrovek]

@geerlingguy I can't say where I work, but I can say that Hashicorp has asked us many times to "please stop using Vagrant, lol" in a "let's give it something for the pain and let it die" kind of way. It's funny to hear them talk about it like that. It's Ruby and everything else of theirs is Go, which I'm sure is a large portion of their desire to retire it.

[ringods]

@naikrovek did they ask you to stop using the Ruby based Vagrant, or Vagrant altogether?

Given their investement in rewriting it in Go, I would be surprised to hear they don't want you to use the upcoming Go based version.

https://www.vagrantup.com/docs/experimental/vagrant_go

[naikrovek]

@naikrovek did they ask you to stop using the Ruby based Vagrant, or Vagrant altogether?

they just sounded kind of exhausted when they said "please don't use vagrant" in the same tone that a very tired parent would say to their child at 4am Saturday morning "please don't jump on my bed to wake me up."

this was a few years ago, perhaps before they made the decision to rewrite. I don't know. I just thought it funny; it has no bearing on this conversation.

[damonbreeden]

Ahrefs uses tart to power (part of) its CI, since many of our developers work day to day on Macs, and M1 is the future of Macs

[zimmski]

We at Symflower are using Tart for our CI. We had dedicated Mac servers before that, but since they are powerful enough we are now splitting them into separate VMs using Tart to maximize our concurrent CI runners. We are testing our product with native ARM64 and over Rosetta2 for x86-64bit. That includes tests running for the console/CI product and for our editor support (VS Code and JetBrains' editors like IntelliJ and GoLand)

So far the experience is really nice! We do have some bugs but i think they are MacOS related and not Tart specific. Let's see. In any case what would be amazing is Kubernetes/Kubevirt suport.

If you need specific information on what we do and how, just let me know. We are open about our setup.