I wrote this four years ago, so instead use this command:
$ docker rmi $(docker images -q -f dangling=true)
NOTE: This is a question I found on StackOverflow which I’ve archived here, because the answer is so effing phenomenal.
If you are not into long explanations, see [Paolo Bergantino’s answer][2].
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
1. When trying to migrate a repo to Github | |
``` | |
git clone --bare ssh://[email protected]:2222/project-name/repo-name.git #clone a bare repo locally | |
curl --header "Authorization: token <GITHUB API TOKEN>" --data '{"name": "repo-name", "description": "Migrated from project-name from gitserver.example.com" https://api.github.com/orgs/org-name/repos #create github repo | |
git push --mirror [email protected]:org-name/repo-name.git | |
``` | |
you'll see an error like this: |
curl --proxy http://127.0.0.1:<tinyproxy-port> https://httpbin.org/ip
. And I don't use any user authentication for proxy, so I locked down the firewall rules with my laptop IP/32.HTTPS_PROXY=<bastion-external-ip>:<tinyproxy-port> KUBECONFIG=my-kubeconfig kubectl get nodes
resource "tls_private_key" "trustanchor_key" { | |
algorithm = "ECDSA" | |
ecdsa_curve = "P256" | |
} | |
resource "tls_self_signed_cert" "trustanchor_cert" { | |
key_algorithm = tls_private_key.trustanchor_key.algorithm | |
private_key_pem = tls_private_key.trustanchor_key.private_key_pem | |
validity_period_hours = 87600 | |
is_ca_certificate = true |