Matthew Yeazel

I believe the issue is the `enabled = true`. `enabled` is only valid for DHCP, static is assumed to be enabled when configured. That should resolve the issue for your...

The file that it is saying doesn't exist is written here: https://github.com/bottlerocket-os/bottlerocket/blob/bd8a944b68814312b52a7ff7abf01208fcfd9d9b/sources/api/netdog/src/cli/generate_net_config.rs#L42 but the error is coming from https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/netdog/src/cli/mod.rs#L84 where it can't find the primary interface file (either interface name...

Thanks @justdan96 for that link. It reminded me of the critical piece here which is the next line configuring netdog. That should be forcing on DHCP for the first interface....

After looking at https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/netdog/src/cli/mod.rs#L182 which parses this configuration. Theoretically it should be able to use that `net.toml` file but I don't know if we have tested using a `net.toml` in...

Hello @AhmadMasry, thanks for cutting this issue! This is currently not supported at the moment but it's something we would like to do in the future. We'll update this ticket...

Sorry @misterek, I should have linked the issue in their GitHub to help explain more about the background: https://github.com/awslabs/mountpoint-s3-csi-driver/issues/86. Essentially the SELinux policies in Bottlerocket are denying this functionality and...

Hello @wokalski! Thanks for cutting this issue! Have you looked at how we build our NVIDIA AWS variants? https://github.com/bottlerocket-os/bottlerocket/blob/develop/variants/aws-k8s-1.28-nvidia/Cargo.toml I haven't tried this since I don't have bare metal NVIDIA...

I took a bit of time to try this out and can confirm the images build just fine for metal: ``` $ git diff diff --git a/variants/metal-k8s-1.28/Cargo.toml b/variants/metal-k8s-1.28/Cargo.toml index d299e025..b7d50ced...

Hello @AhmadMS1988, we do not have plans to move to 6.6 for `aws-k8s-1.30`. We track the same long term releases as Amazon Linux and the latest they are tracking is...

From reading your issue, it seems that the `ext4` filesystem is likely not committing to disk quickly enough for that initial power cycle. The `BOTTLEROCKET-PRIVATE` partition is [mounted with](https://github.com/bottlerocket-os/bottlerocket/blob/40290daacde40b37c6e8e9d0fb22338d9b23f819/packages/release/var-lib-bottlerocket.mount#L9) `Options=defaults,nosuid,nodev,noexec,noatime,private,context=system_u:object_r:private_t:s0`...