-
> 우선 stack 에서 지원 가능한 지만, 1차 조사
### 소개
https://aws.amazon.com/ko/amazon-linux-ami/
https://aws.amazon.com/marketplace/pp/B00635Y2IW
### 패키지 업데이트 내역
https://aws.amazon.com/ko/amazon-linux-ami/2016.03…
-
**Describe the bug**
Spice runtime does not start on [Amazon Linux 2023 AM](https://aws.amazon.com/amazon-linux-ami/)I (`al2023-ami-2023.5.20240701.0-kernel-6.1-x86_64`) - default Linux image when …
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
**Describe the bug**
vizier-pem can't initialize BPF program in Kernel, because an undeclared function `arch_ftrace_get_regs`. the impact of this, of course, i'm only receiving a subset of metrics (C…
-
**Describe the bug**
The pods fail to run on EKS Nodes which are using AL2023 instead of AL2:
```
{"level":"info","ts":"2024-05-14T10:15:35Z","msg":"version","GitVersion":"v2.7.2","GitCommit":"fb…
-
The use of the recommended ECS-Optimized AMIs is great, let's migrate it though to use the Amazon Linux 2 ones.
-
I spun up an EC2 instance since I don't have access to a machine with 16GB of RAM (and I had difficultly installing libavl on OS X), cloned the repo, installed a libavl RPM (since it's not part of the…
-
Hello,
When running `trivy-action` scans on ECS-Optimized Amazon Machine Images (AMIs) in a GitHub Actions workflow, I've found Trivy fails to detect the operating system and reports a 'filesystem …
-
Getting the following error -
Error: could not create cluster provider from options: managedNodeGroups[0].overrideBootstrapCommand is not supported when using a custom AMI based on AmazonLinux2023 (…
-
│ Error: Your query returned no results. Please change your search criteria and try again.
│
│ with data.aws_ami.amazon-linux,
│ on instances.tf line 9, in data "aws_ami" "amazon-linux":
│ …