I tried installing the tools normally and ran into multitudes of weirdness. On my old laptop I’d typically use homebrew for managing packages and RVM (and previously rbenv) for ruby version management in different projects. My first step in starting with a new machine was to get my development environment setup. M1 Mac Mini ensconced beneath multitudes of cables in my home office However, upon trying to do make some updates to a recent project (by the way, we launched our new staff directory!) I ran into many stumbling blocks.

Since roughly a year had passed since these new machines had been introduced I assumed the kinks would have been generally worked out and I was excited to give my speedy new M1 Mac Mini a test run at some serious work. PS: Found here something - but not sure if this connected with my issue and makes sense.Due to a battery issue with my work laptop (an Intel-based MacBook pro), I had an opportunity to try using a newer (ARM-based) M1 Mac to do development work. Or processor type / flags must be configured differently. So there seems to be a bug in the current UTM version regarding UUIDD/random number generation. I've tried again with an older utm version (3.2x) and it worked. However, I did not quite understand why not.Somehow it seems to be related to the emulation of the Intel processor by UTM/quemu. After some investigation I've found out that the HDBDeamon could not start because some uuidd service dumped/did not start on docker image linux layer. Which obviously could not have been the real reason. Hint: Container must have at least 70GB DISK free Hint: Container must have at least 16GB RAM available Hint: docker containers can be joined by: docker exec -it bash You can try your luck 10 times until initialization is terminated The service HDB has failed to start and initialization is blocked until the problem is resolved HDB: the start command failed, exit code=2 StartWaitįAIL: process hdbdaemon HDB Daemon not running

I've played recently again around with the abaptrial docker image and was not able to get that image running.

Running docker on mac m1