Playing around with Podman 1 alias docker="sudo podman $1" The above command works as of this time and podman makes namespaces for every users for every resources, i.e., images, containers and so on. It means, podman images and sudo podman images will show different resources.😎 1 2 3 4 5 sudo podman pod create --name my-pod -p 8080:80 sudo podman run -d --restart=always --pod=my-pod --name my-nginx nginx sudo podman run -d --restart=always --pod=my-pod --name my-curl curl sudo podman generate kube my-pod > my-pod.

Kubectl Installation 1 2 3 4 curl -LO "https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl" chmod +x kubectl echo $PATH sudo mv kubectl /usr/local/bin/ Minikube Installation 1 2 3 4 5 curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 chmod +x minikube-linux-amd64 sudo mv minikube-linux-amd64 /usr/local/bin/minikube minikube start minikube status Kubectl Commands CRUD Commands 1 2 3 kubectl create deployment [name] kubectl edit deployment [name] kubectl delete deployment [name] Status of different K8s components 1 kubectl get `nodes | pods | services | replicasets | deployments` Debugging pods 1 2 Kubectl logs [pod name] kubectl exec -it containername -- bin/bash Applying YAML files 1 2 3 4 5 6 7 8 9 10 kubectl apply -f some-deployment.

This article is based on the content of aws knowledgebase. You might have been stuck in memory leak when building some kinda javascript-heavy frontend apps like Vue or React on a cloud server itself. Just for serving built artifacts, we do not need large instances, but still the building process is always hungry for more memory you know. Below is how to resolve such specific problem. Oh, this is not the case if you already have a dedicated(partitioned) swap space, it’s a better option in any case but in most cases, we will be playing with servers without a swap patition.

This article is based on the contents of the Github’s documentation. You will get your own verified badge on every git commits once you configure your GPG key with your VCS. First things first, check your gpg version using this command: 1 gpg --version Allow me to assume that you are on version 2.1.17 or greater. Use this command to generate a GPG key: 1 gpg --full-generate-key Choose the default for kind of key and give 4096 for key size, choose 0 for expiration time or up to your decision otherwise.

I have just finished migrating my blog from Ghost self-hosting to Hugo. I am more than happy to use: { framework: “Hugo”, hosting: “Firebase”, cicd: “CircleCI” }. I just wanted to share the full process of how I got it done, which was not a piece of cake. You see, it’s not a toy project, it’s real one. There are plenty of great resources available that explain how to setup Hugo, install Hugo themes, and so on.