F………………………………………………………………………………..
https://www.preining.info/blog/2018/05/docker-cron-mail-and-logs/
from debian:stretch-slim RUN apt-get -y update RUN apt-get install -y cron #ssmtp ADD . /app ADD crontab /etc/cron.d/mypackage RUN chmod 0644 /etc/cron.d/mypackage #ADD ssmtp.conf /etc/ssmtp/ssmtp.conf #RUN chown root.mail /etc/ssmtp/ssmtp.conf #RUN chmod 0640 /etc/ssmtp/ssmtp.conf CMD cron -f =====
docker-compose.yml version: '3.3' services: gethpeers: build: context: gethpeers/ volumes: - cronlog:/app/cronapplog:rw networks: - fastdev fakelog: build: context: fakelog/ volumes: - cronlog:/app/cronapplog:rw - filebeat:/usr/share/filebeat/data:rw networks: - fastdev volumes: cronlog: filebeat: networks: fastdev: driver: bridge gethpeers Dockerfile from debian:stretch-slim RUN apt-get -y update RUN apt-get install -y cron #ssmtp ADD .
https://www.reddit.com/r/docker/comments/9j2vc7/migrating_to_kubernetes_from_dockercompose_in/
If / when you’re able to spawn arbitrary VMs, you can look at kubeadm, CoreOS, RKE (my current choice), and so on for cluster creation.
Before you can use kompose, or use kubectl apply -f myawesome.yaml, you first and foremost need to set up a Kubernetes cluster. This might be the most challenging thing to do because Kubernetes is heavy-weight compared to docker-compose. I recommend using RKE to set it up.
https://rancher.com/docs/rke/v0.1.x/en/config-options/add-ons/user-defined-add-ons/
To define an add-on directly in the YAML file, make sure to use the YAML’s block indicator
|- as the addons directive is a multi-line string option. It’s possible to specify multiple YAML resource definitions by separating them using the
-– directive.
https://kubernetes.github.io/ingress-nginx/examples/docker-registry/
https://sueboy.blogspot.com/2019/11/kubernetes-nodeport.html
PS：Close basic auth just remark configmap.yml auth: #auth: # htpasswd: # realm: basic-realm # path: /auth/htpasswd README.md
# Docker Registry K8s Domain：docker-registry Port:30500 /etc/hosts add 192.168.99.118 docker-registry ## ip is k8s host eth2's ip Finish command： docker login -u username -p password docker-registry:30500 [](https://3.bp.blogspot.com/-Wj82n6nvHkw/XHUVI-gNy7I/AAAAAAAAUE8/rs1l8mQuu8cKvkoMcZGn0lOfJUWY3udMgCLcBGAs/s1600/dockerloginsuccess.jpg) https://docs.docker.com/registry/insecure/ Deploy a plain HTTP registry ---------------------------- ```bash /etc/docker/daemon.json { "insecure-registries" : ["docker-registry:30500"] } Restart Docker for the changes to take effect https://blog.
1、install Virtualbox
2、donwload & rename minikube.exe & move minikube.exe put file on path C:\minikube
add path to system PATH
https://storage.googleapis.com/minikube/releases/latest/minikube-windows-amd64.exe
3、download kubectl.exe put file on path C:\minikube
https://storage.googleapis.com/kubernetes-release/release/v1.13.0/bin/windows/amd64/kubectl.exe
4、minikube start
5、check virtualbox have new minikube
PS：Don’t start minikube with Virtualbox UI. Use cmd >minikube start 6、Run
> minikube dashboard
7、Get IP
> minikube ip
1. create htpasswd
docker run --rm --entrypoint htpasswd registry:2 -Bbn username password > htpasswd docker run --rm --entrypoint htpasswd registry:2 -Bbn test test > htpasswd htpasswd file inside have two records: username & test
2. create registry_config.yml
version: 0.1 log: fields: service: registry storage: delete: enabled: true cache: blobdescriptor: inmemory filesystem: rootdirectory: /var/lib/registry http: addr: :5000 headers: X-Content-Type-Options: [nosniff] Access-Control-Allow-Origin: ['*'] Access-Control-Allow-Methods: ['HEAD', 'GET', 'OPTIONS', 'DELETE'] Access-Control-Allow-Headers: ['Authorization'] Access-Control-Max-Age: [1728000] Access-Control-Allow-Credentials: [true] Access-Control-Expose-Headers: ['Docker-Content-Digest'] auth: htpasswd: realm: basic-realm path: /etc/docker/registry/htpasswd Access-Control-Allow-Origin can change you want.
