containers-roadmap
netshoot
Our great sponsors
containers-roadmap | netshoot | |
---|---|---|
80 | 24 | |
5,142 | 7,633 | |
0.7% | - | |
2.0 | 3.6 | |
9 months ago | 21 days ago | |
Shell | Shell | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
containers-roadmap
-
General Availability of the AWS SDK for Rust
Thanks for showing up and answering questions. Congratulations on the release.
What kind of plans for support of Rust's evolving async ecosystem?
Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1
Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically
-
Architecting for Resilience: Crafting Opinionated EKS Clusters with Karpenter & Cilium Cluster Mesh โ Part 1
Second, We will only rely on one managed node group, but we will leverage Karpenter; however, karpenter needs to be deployed on a node. (This may change soon once the Karpenter is available on the EKS Control Plane.) [EKS] Karpenter inside control plane ยท Issue #1792 ยท aws/containers-roadmap
-
Running a Web Application with 100% AWS Fargate Spot Containers ๐ค
As written in the AWS documentation, during periods of extremely high demand, Fargate Spot capacity might be unavailable. In concrete terms, if your ECS service is set up to execute tasks in 100% Spot, there is a risk of running out of capacity. A workaround has been created in the hope that one day this issue will be implemented by the AWS team. This workaround allows you to set up two ECS services :
-
Kubernetes SidecarContainers feature is merged
Deploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.
If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else
https://github.com/aws/containers-roadmap/issues/696
- AWS Config supports recording exclusions by resource type
- Announcing pull through cache for registry.k8s.io in Amazon Elastic Container Registry
-
EKS/Spot vs EKS Fargate/Spot?
Eks Fargate doesn't support spot yet https://github.com/aws/containers-roadmap/issues/622
- audit logging of the master plane in EKS
-
How to use Podman inside of a container
Until podman could be used with AWS ECR/ECS it's pretty much moot in my case: https://github.com/aws/containers-roadmap/issues/626
- How to keep 100% availability with a single ec2 spot instance?
netshoot
- Docker Container Can't Ping
- Vaultwarden docker container with internal network
- Internet not working inside any Kubernetes pod
-
Docker Networking: A Step-by-Step Guide for Developers
Now, let's use netshoot, a Docker image equipped with a set of networking troubleshooting tools that can be used for Docker networking.
- Has the image netshoot the Alpine/musl DNS issues?
-
What's your favourite Docker Image, and why?
nicolaka/netshoot for sure. having a preloaded array of networking troubleshooting tools in an image for kubernetes debugging is a godsend.
- k8s docker image with basic troubleshooting tools
-
Networking lab for learning using containers?
First off, it seems like getting tcpdump or Wireshark to capture from the container network and dumping to a file will take some extra steps. (A lot of blog posts seem to recommend this Github project - https://github.com/nicolaka/netshoot)
- qBittorrent "Error" after putting the container through a Gluetun container
-
New to ubuntu and stumped by my cloudflare tunnels suddenly no longer working...
Some hints how to debug such problems in the future: 1. ufw drops/rejections are logged (use dmesg to view them) 2. wireshark shows all connection attempts, even those that are blocked by firewall 3. ss or netstat shows if the server is actually listening for connections 4. netshoot allows to enter docker container network namespace and do pings, curl or telnet from there
What are some alternatives?
eks-nvme-ssd-provisioner - EKS NVMe SSD provisioner for Amazon EC2 Instance Stores
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
kube-fledged - A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
ksniff - Kubectl plugin to ease sniffing on kubernetes pods using tcpdump and wireshark
kraken - P2P Docker registry capable of distributing TBs of data in seconds
container_builder - This project builds containers images using Ansible. The containers are defined as hosts in the Ansible inventory. They are generated using host and group variables, templates and local connection.
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
geodesic - ๐ Geodesic is a DevOps Linux Toolbox in Docker
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
Filestash - ๐ฆ A modern web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ...
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
docker-zulip - Container configurations, images, and examples for Zulip.