coreos

Should I use forever/pm2 within a (Docker) container?

由 牧云@^-^@ 提交于 2019-11-28 16:28:04
问题 I am refactoring a couple of node.js services. All of them used to start with forever on virtual servers, if the process crashed they just relaunch. Now, moving to containerised and state-less application structures, I think the process should exit and the container should be restarted on a failure. Is that correct? Are there benefits or disadvantages? 回答1: My take is do not use an in-container process supervisor (forever, pm2) and instead use docker restart policy via the --restart=always

How to fix Docker's “Error pulling image…too many redirects” failures while pulling images from registry?

由 ↘锁芯ラ 提交于 2019-11-28 05:20:50
I am running Docker via CoreOS and Vagrant on OS X 10.10. When I run docker pull ubuntu in CoreOS, I got following errors: $ docker pull ubuntu Pulling repository ubuntu cc0067db4f11: Error pulling image (precise) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/, Get https://cdn-registry-1.docker.io/v1/images/cc0067db4f11198ef6fd0435f96a973e559b1cebfceb2bc8e4fe527b32045c2f/ancestry: dial tcp: lookup cdn-registry-1.dcc0067db4f11: Error pulling image (precise) from ubuntu, Get https://cdn-registry-1.docker.io/v1/images/cc0067db4f11198ef6fd0435f96a973e559b1cebfceb2bc8e4fe527b32045c2f

kubernetes service IPs not reachable

由 泪湿孤枕 提交于 2019-11-28 01:10:01
问题 So I've got a kubernets cluster up and running using the Kubernetes on CoreOS Manual Installation Guide. $ kubectl get no NAME STATUS AGE coreos-master-1 Ready,SchedulingDisabled 1h coreos-worker-1 Ready 54m $ kubectl get cs NAME STATUS MESSAGE ERROR controller-manager Healthy ok scheduler Healthy ok etcd-0 Healthy {"health": "true"} etcd-2 Healthy {"health": "true"} etcd-1 Healthy {"health": "true"} $ kubectl get pods --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE

Issues running cron in Docker on different hosts

由 跟風遠走 提交于 2019-11-27 21:33:17
问题 Im trying to get a docker container running to mange my cronjobs im running a very simple cron as a test in a docker container using centOS 6.5 base * * * * * /bin/echo "it works!" >> test.log it works fine if the container is running on CoreOS host, however if I run the container on a ubuntu 13.10 host the cron is not executed. (I though the host did not effect what was running in the container) both hosts are running docker 0.8 am I missing something obvious, or it this a bug? thanks 回答1:

Pulling images from private registry in Kubernetes

由 痴心易碎 提交于 2019-11-27 19:04:22
I have built a 4 node kubernetes cluster running multi-container pods all running on CoreOS. The images come from public and private repositories. Right now I have to log into each node and manually pull down the images each time I update them. I would like be able to pull them automatically. I have tried running docker login on each server and putting the .dockercfg file in /root and /core I have also done the above with the .docker/config.json I have added secret to the kube master and added imagePullSecrets: name: docker.io to the Pod configuration file. When I create the pod i get the

Allow scheduling of pods on Kubernetes master?

由 ﹥＞﹥吖頭↗ 提交于 2019-11-27 03:21:28
问题 I set up Kubernetes on CoreOS on bare metal using the generic install scripts. It's running the current stable release, 1298.6.0, with Kubernetes version 1.5.4. We'd like to have a highly available master setup, but we don't have enough hardware at this time to dedicate three servers to serving only as Kubernetes masters, so I would like to be able to allow user pods to be scheduled on the Kubernetes master. I set --register-schedulable=true in /etc/systemd/system/kubelet.service but it still

How to fix Docker's “Error pulling image…too many redirects” failures while pulling images from registry?

由 耗尽温柔 提交于 2019-11-27 00:54:23
问题 I am running Docker via CoreOS and Vagrant on OS X 10.10. When I run docker pull ubuntu in CoreOS, I got following errors: $ docker pull ubuntu Pulling repository ubuntu cc0067db4f11: Error pulling image (precise) from ubuntu, endpoint: https://cdn-registry-1.docker.io/v1/, Get https://cdn-registry-1.docker.io/v1/images/cc0067db4f11198ef6fd0435f96a973e559b1cebfceb2bc8e4fe527b32045c2f/ancestry: dial tcp: lookup cdn-registry-1.dcc0067db4f11: Error pulling image (precise) from ubuntu, Get https:

ETCD：在容器中运行etcd集群

由 牧云@^-^@ 提交于 2019-11-26 12:26:21
原文地址： Docker container 以下指南显示了如何使用 静态引导过程 在rkt和Docker上运行etcd。 rkt 运行单节点的etcd 以下rkt run命令将在端口2379上公开etcd客户端API，并在端口2380上公开对等API。 配置etcd时使用主机IP地址。 export NODE1=192.168.1.21 信任CoreOS App签名密钥 。 sudo rkt trust --prefix quay.io/coreos/etcd # gpg key fingerprint is: 18AD 5014 C99E F7E3 BA5F 6CE9 50BD D3E0 FC8A 365E 运行etcd v3.2版本或指定其他发行版本。 sudo rkt run --net=default:IP=${NODE1} quay.io/coreos/etcd:v3.2 -- -name=node1 -advertise-client-urls=http://${NODE1}:2379 -initial-advertise-peer-urls=http://${NODE1}:2380 -listen-client-urls=http://0.0.0.0:2379 -listen-peer-urls=http://${NODE1}:2380 -initial
订阅 coreos