KVM+QEMU in this experiment, I am trying to launch macOS in a docker from Ubuntu 1804 installed to a WSL2 VM. https://github.com/sickcodes/Docker-OSX#id-like-to-run-docker-osx-on-windows environment host OS: Windows 11 Home CPU: AMD Ryzen 5 4500U with Radeon Graphics 2.38 GHz vm…

CVE-2021–23567 I am exploring how chatGPT could help to create some exploit code for known CVE. prompt: answer from chatGPT:

a quick way to tell whether a port is being used in Linux python3 -m http.server 8080 --bind 0.0.0.0 when port is available, it shows Serving HTTP on 0.0.0.0 port 8081 (http://0.0.0.0:8081/) ... when it is already occupied, it shows Traceback (most recent call last): File "/usr/lib/python3.8/runpy.py", line 194…

To expose a service in a on prem k8s cluster, you just need to add a ingress controller and map out the service and port, however, things are little bit trickier with WSL2…. first, WSL2 doesn’t allow port forwarding AFTER you have created the cluster. secondly, a minor but annoying…

To cut long story short, I need to create a private RDS instance for EKS to access; and to do that, I need to create RDS in the same subnet as EKS; and, because my hands are itchy, I decided to do that via ACK (AWS controller for Kubernetes). And…

RUN is an image build step, the state of the container after a RUN command will be committed to the container image. A Dockerfile can have many RUN steps that layer on top of one another to build the image. CMD is the command the container executes by default when…

I am starting from a freshly install WSL2 environment, so my first step is to download my SSH key and connect to an EC2 instance where I already have awscli and kubectl installed. chmod 600 SG-xxx.pem ssh -i "SG-xxx.pem" ubuntu@ec2-1-2-3-4.ap-southeast-1.compute.amazonaws.com then check and set the current context to my EKS: …

When I was trying to deploy nginx ingress on KIND in windows subsystem Linux (WSL2) environment, kubectl apply --filename https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/kind/deploy.yaml kubectl wait --namespace ingress-nginx \ --for=condition=ready pod \ --selector=app.kubernetes.io/component=controller \ --timeout=180s kubectl apply --filename nginx-ingress.yaml

To begin with, ingressController is a service ingress is a k8s resource type so you could list all ingress with k get ingress -A NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE app-space ingress-wear-watch <none> * 80 31s you had to list all ingress controller with k get svc -A |grep…