Zac
Zac
@baasumo Thanks for following up on this!
Thanks for the report! A few questions for my info: * How was the Bottlerocket image provisioned? Via EKS-A or by hand? * Could you provide any output of what...
I would also be curious to see what `/proc/consoles` contains on the machine in question... If it actually finished booting and a user could get to a configured admin container...
Following up on this: I found that EKS-A has [default console settings](https://github.com/aws/eks-anywhere/blob/44c2fc11a9b40a854cb2eb7a6f3a5e9bcabbfece/pkg/api/v1alpha1/tinkerbelltemplateconfig_defaults.go#L27-L28): `console=tty0 console=ttyS0,115200n8`. That means that when you provisioned with EKS-A without any customization all systemd output was going...
Closing this out as the EKS-A PR has been merged! The next EKS-A release should have these changes included.
Hi @backjo ! Thanks for bringing this to our attention; I barely remember discussing those things in the very early days of Bottlerocket. :) Are you running into these limits...
I'm a little curious about this motivation behind this change! Also, assuming this all came up via compiler errors, but one nice thing about implementing `TryFrom` means you can use...
Thanks for letting us know - we'll take this into consideration when planning and considering if or how we can make this more configurable.
Upstream issue: https://github.com/containerd/containerd/issues/6063
PR: https://github.com/containerd/containerd/pull/6064