Skip to content. | Skip to navigation

Personal tools

Navigation

You are here: Home / Tips / Container

Container

Docker https://medium.com/@brunoamaroalmeida/how-to-transparently-use-a-proxy-with-any-application-docker-using-iptables-and-redsocks-b8301ddc4e1e https://medium.com/@vikram.fugro/project-calico-the-cni-way-659d057566ce

Docker on AWS Dockerize Acceptance Tests Kubernetes Guide for Docker Swarm Users Docker Remote Interpreter using PyCharm Jenkins and Kubernetes with Docker Desktop

PyPI Container eea.docker.plone

$ sudo docker run -t -i -p 8090:8080 marr/plone:v500 /bin/bash
docker run -d -p 8080:80 -h pypi.local -v /shares/pypi:/srv/pypi:rw --name pypi docker.io/codekoala/pypi:latest
chcon -Rt svirt_sandbox_file_t /shares/pypi
updated ~/.pypirc to reflect the internal server

port 對應方式的討論

 $ sudo docker login
Username: marr
Password:
Email: ooxx@xyz.com
WARNING: login credentials saved in /home/user/.docker/config.json
Login Succeeded
$ sudo docker push marr/plone
The push refers to a repository [docker.io/marr/plone] (len: 1)
...
v500: digest: sha256:....
635d6 size: 58915

Plone 範例 預設已包含 ZeoServer 執行形式 IMIO Example Storage Location Settings docker-compose-setup UnifiedInstaller help script: su-exec tiny

Remove Image Container Volumn

Makefile Example jupyter with Nix Ubuntu 12.04 測試 http://datakurre.pandala.org/2015/07/building-docker-containers-from-scratch.html 產生下列錯誤

Error: Error downloading extends for URL https://dist.plone.org/release/5-latest/versions.cfg: (SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)'),)

Dockerfile LABEL 協助標示 ENTRYPOINT & CMD

Docker Compose for Local Development

DockerFile for Plone

Windows + WSL

Data Storage

Data Volume 依開發或服務模式來設定

Image

clair: Check Images for Vulnerabilities

testthedocs: ttd-textlint Linting Tool for Text as Container

Application Health Check with Golang and Multi-Stage Docker Build

react AWS fargate

Ansible

AttributeError Relationalist Object Has no Attribute source

ansible-playbook SSL Configuration Kubernetes implements health checks using readiness and liveness probes. A readiness probe is used to determine if a Pod can serve traffic. Failure of a readiness probe would result in the Pod being removed from the Endpoints that make up a Service, resulting in the Pod not being routed any traffic until the readiness probe succeeds. A liveness probe, on the other hand, is used to indicate if a service is responsive or if it’s hung or deadlocked. The failure of a liveness probe results in the kubelet restarting the individual container. https://medium.com/@copyconstruct/health-checks-in-distributed-systems-aa8a0e8c1672