| 15 Oct 2024 |
 commiterate | and the long instance scrubbing is due to the processes Apple needs for firmware and software updates | 18:32:36 |
| commiterate | you can skip scrubbing from instance stop and terminate with a root volume replacement though | 18:32:47 |
 Arian | Even when you keep the host reservation changing the AMI takes a few hours though ;/ | 18:33:02 |
| commiterate | but eventually you must go through a scrubbing cycle if you want updated firmware | 18:33:04 |
| Arian | Ah didn't know that | 18:33:08 |
| commiterate | I also talked with the ASG PMs and they're looking at root volume replacement for instance refresh | 18:33:28 |
| commiterate | but yeah due to Apple's EULA, Mac instances are the most inelastic instances of all time | 18:33:42 |
| commiterate | since elasticity requires it to be fast to take from and return to the free capacity pool | 18:33:58 |
| commiterate | which Mac instances are the antithesis of | 18:34:02 |
| commiterate | EC2 is trying to get Apple to change their stance but the PM says they're quite adamant and will probably take like 1-3 years time | 18:36:04 |
| Arian | My workaround so far has been spawning VMs on the instances using virtualization framework | 18:44:56 |
| Arian | :) | 18:45:00 |
| commiterate | yeah same. Need to use Tart VMs for isolation anyways. | 18:45:28 |
| Arian | Yeh so we just register tart VMs to GHA basically | 18:45:44 |
| Arian | Spawning a fresh VM per job | 18:45:50 |
| commiterate | I'm probably just going to delay working on macOS GitLab runners since they make deployments horrible.
I'm really just using the Nix profiles trick for bootstrap Docker runners that use Amazon Linux 2023 + Nix profiles. Those bootstrap machines will guarantee a build machine pool for platform-specific artifacts (e.g. NixOS images) which will support the actual production pool. | 18:47:28 |
| commiterate | But mentioning macOS in the issue specifically gets around the "why aren't you just using NixOS" questions. | 18:47:59 |
| 17 Oct 2024 |
|  Mic92 changed their display name from Mic92 to Mic3000. | 06:51:17 |
| Mic92 changed their display name from Mic3000 to Mic3000 🌋. | 06:51:46 |
| Mic92 changed their display name from Mic3000 🌋 to Mic92. | 12:22:31 |
| 18 Oct 2024 |
| Arian | Could somebody have a look at this R? https://github.com/NixOS/nixpkgs/pull/343939 | 08:04:55 |
 @AleXoundOS:matrix.org | In reply to @arianvp:matrix.org
Could somebody have a look at this R? https://github.com/NixOS/nixpkgs/pull/343939 Does it mean that t2.micro won't be supported? | 15:09:25 |
| Arian | In reply to @AleXoundOS:matrix.org
Does it mean that t2.micro won't be supported? It will! I even tested it | 15:12:36 |
| Arian | It supports both bios and uefi with this image | 15:12:44 |
| @AleXoundOS:matrix.org | In reply to @arianvp:matrix.org
It supports both bios and uefi with this image (Sorry for bothering. Just wanted to be sure.) | 15:13:37 |
| Arian | It's a good question to ask :) | 15:15:10 |
| @AleXoundOS:matrix.org | The AWS CLI command at https://nixos.github.io/amis/ is misleading. There are 2 consecutive --filter options used. However, when I tested only the last one is being applied.
This works instead:
aws ec2 describe-images --owners 427812963091 --filters 'Name=name,Values=nixos/24.05*' 'Name=architecture,Values=arm64'
| 15:27:25 |
| @AleXoundOS:matrix.org | * The AWS CLI command at https://nixos.github.io/amis/ is misleading. There are 2 consecutive --filter options used. However, when I tested only the last one is being applied.
This works instead:
aws ec2 describe-images --owners 427812963091 \
--filters 'Name=name,Values=nixos/24.05*' 'Name=architecture,Values=arm64'
| 15:27:41 |
| @AleXoundOS:matrix.org | * The AWS CLI command at https://nixos.github.io/amis/ is misleading. There are 2 consecutive --filter options used. However, when I tested only the last one is being applied.
This works instead:
aws ec2 describe-images --owners 427812963091 \
--filters 'Name=name,Values=nixos/24.05*' 'Name=architecture,Values=arm64'
| 15:27:51 |
| Arian | Oh that's a typo then! Can you send a PR? | 16:10:35 |
