Início / user-206348

Mohammed Ali's questions

Martin Hope
Mohammed Ali
Asked: 2018-04-10 21:13:19 +0800 CST
  • 0

Eu tenho uma situação em que tenho a saída de um comando, assim,

192.168.1.84
192.168.1.85

eu quero usar isso e fazer alterações em outro arquivo, ou seja, adicionar esses endereços IP um após o outro, como neste formulário. Abaixo da linha ResourceRecordSet .

ubuntu@kops:/mujahid$ cat change-resource-record-sets.json
{
    "Comment": "Update record to reflect new IP address of home router",
    "Changes": [
        {
            "Action": "UPSERT",
            "ResourceRecordSet": {
                "Name": "testing.mak.online.",
                "Type": "A",
                "TTL": 60,
                "ResourceRecords": [
                    {
                        "Value": "192.168.1.84"
                    },
                    {
                        "Value": "192.168.1.5"
                    }
                ]
            }
        }
    ]
}
shell-script shell
Martin Hope
Mohammed Ali
Asked: 2018-01-17 06:27:19 +0800 CST
  • 1

Estou executando este playbook, mas está falhando na última tarefa. executando isso do host ubuntu,,

---
 - hosts: all
   become: yes
   tasks:
   - name: Copy certificate files.
     copy:
        src: "{{ item.src }}"
        dest: "{{ item.dest }}"
        owner: root
        group: root
        mode: 0644
     with_items:
     -  {  src: "/registry_certs/domain.crt", dest: "/usr/local/share/ca-certificates/ca.crt" }

   - command: sudo apt-get install --reinstall ca-certificates
   - command: sudo update-ca-certificates

   - name:  "just force systemd to reread configs (2.4 and above)"
     systemd:
       name: "{{ item }}"
       state: started
       daemon_reload: yes
     with_items:
     - docker
     - kubelet

erro

ubuntu@kops:/etc/ansible$ sudo ansible-playbook certificate_new.yml -l aws  --syntax-check
ERROR! no action detected in task

The error appears to have been in '/etc/ansible/certificate_new.yml': line 18, column 6, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


   - name:  "just force systemd to reread configs (2.4 and above)"
     ^ here
debian ansible
Martin Hope
Mohammed Ali
Asked: 2017-12-24 06:21:23 +0800 CST
  • 2

Eu configurei um registro privado no docker acessível por meio de um domínio “makdom.ddns.net”, posso fazer o login push e pull de imagens localmente, sem problemas, mesmo a partir do nó kubes escravo, posso fazer isso,

mas quando escrevo um arquivo de implantação do kubes, ele não consegue extrair imagens do registro privado e falha.

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: ssh-deployment
spec:
  template:
    metadata:
      labels:
        app: helloworld
    spec:
      containers:
      - name: ssh-demo
        image: makdom.ddns.net/my-ubuntu
        imagePullPolicy: IfNotPresent
        ports:
        - name: nodejs-port
          containerPort: 22
      imagePullSecrets:
      - name: myregistrykey

segredos:

DOCKER_REGISTRY_SERVER="https://makdom.ddns.net/v1/"
DOCKER_USER="user"
DOCKER_PASSWORD="password"
DOCKER_EMAIL="[email protected]" 

kubectl create secret docker-registry myregistrykey \
  --docker-server=$DOCKER_REGISTRY_SERVER \
  --docker-username=$DOCKER_USER \
  --docker-password=$DOCKER_PASSWORD \
  --docker-email=$DOCKER_EMAIL

erro:

Events:
  Type     Reason                 Age               From                  Message
  ----     ------                 ----              ----                  -------
  Normal   Scheduled              1m                default-scheduler     Successfully assigned ssh-deployment-7b7c7bf977-m6stk to kubes-slave
  Normal   SuccessfulMountVolume  1m                kubelet, kubes-slave  MountVolume.SetUp succeeded for volume "default-token-mx7qq"
  Normal   Pulled                 1m (x3 over 1m)   kubelet, kubes-slave  Container image "makdom.ddns.net/my-ubuntu" already present on machine
  Normal   Created                1m (x3 over 1m)   kubelet, kubes-slave  Created container
  Normal   Started                1m (x3 over 1m)   kubelet, kubes-slave  Started container
  Normal   Pulling                34s (x2 over 1m)  kubelet, kubes-slave  pulling image "makdom.ddns.net/my-ubuntu"
  Warning  Failed                 34s (x2 over 1m)  kubelet, kubes-slave  Failed to pull image "makdom.ddns.net/my-ubuntu": rpc error: code = Unknown desc = Error: image my-ubuntu:latest not found
  Warning  Failed                 34s (x2 over 1m)  kubelet, kubes-slave  Error: ErrImagePull
  Warning  BackOff                19s (x6 over 1m)  kubelet, kubes-slave  Back-off restarting failed container
docker kubernetes
Martin Hope
Mohammed Ali
Asked: 2017-12-16 02:02:50 +0800 CST
  • 1

Alguém sabe como se conectar a um uri de host do docker? eu preciso configurar o jenkins para executar tarefas em um host do docker? Esta é a informação do host do docker. Esta é uma máquina baseada no Ubuntu.

root@node1:~# netstat -tulnp | grep LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1263/sshd
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      3526/0
tcp        0      0 127.0.0.1:6011          0.0.0.0:*               LISTEN      3793/1
tcp6       0      0 :::22                   :::*                    LISTEN      1263/sshd
tcp6       0      0 ::1:6010                :::*                    LISTEN      3526/0
tcp6       0      0 ::1:6011                :::*                    LISTEN      3793/1
root@node1:~#
root@node1:~#
root@node1:~# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-12-14 06:44:46 UTC; 1 day 2h ago
     Docs: https://docs.docker.com
 Main PID: 1249 (dockerd)
    Tasks: 17
   Memory: 69.5M
      CPU: 2min 233ms
   CGroup: /system.slice/docker.service
           ├─1249 /usr/bin/dockerd -H fd://
           └─1401 containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libco

Dec 14 06:44:46 node1 dockerd[1249]: time="2017-12-14T06:44:46.551798058Z" level=info msg="Daemon has completed initialization"
Dec 14 06:44:46 node1 dockerd[1249]: time="2017-12-14T06:44:46.551973729Z" level=info msg="Docker daemon" commit=092cba3 graphdriver=aufs version=1.13.1
Dec 14 06:44:46 node1 systemd[1]: Started Docker Application Container Engine.
Dec 14 06:44:46 node1 dockerd[1249]: time="2017-12-14T06:44:46.580061946Z" level=info msg="API listen on /var/run/docker.sock"
Dec 15 06:41:09 node1 dockerd[1249]: time="2017-12-15T06:41:09.897610342Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version sp
Dec 15 06:41:09 node1 dockerd[1249]: time="2017-12-15T06:41:09.900105358Z" level=warning msg="failed to retrieve docker-init version: unknown output format: tini ver
Dec 15 08:56:46 node1 dockerd[1249]: time="2017-12-15T08:56:46.836355744Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version sp
Dec 15 08:56:46 node1 dockerd[1249]: time="2017-12-15T08:56:46.838301865Z" level=warning msg="failed to retrieve docker-init version: unknown output format: tini ver
Dec 15 09:06:19 node1 dockerd[1249]: time="2017-12-15T09:06:19.272709345Z" level=warning msg="failed to retrieve runc version: unknown output format: runc version sp
Dec 15 09:06:19 node1 dockerd[1249]: time="2017-12-15T09:06:19.274916674Z" level=warning msg="failed to retrieve docker-init version: unknown output format: tini ver
docker jenkins