Welcome to the Linux Foundation Forum!

LFD259 Lab 3.2 - cannot push correctly to local repo

Options

Greetings ... having an issue with this lab at the point where I push to the local repo.
The registry appears to be running

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/nginx 1/1 1 1 18m
deployment.apps/registry 1/1 1 1 18m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 443/TCP 2d19h
service/nginx ClusterIP 10.111.191.243 443/TCP 17h
service/registry ClusterIP 10.107.252.139 5000/TCP 17h

NAME READY STATUS RESTARTS AGE
pod/nginx-65478f7767-2p7sz 1/1 Running 0 18m
pod/registry-7ccd695dc7-wcgvj 1/1 Running 0 18m

I have this in /etc/docker/daemon.json

{
"exec-opts": ["native.cgroupdriver=systemd"],
"log-driver": "json-file",
"log-opts": {
"max-size": "100m"
},
"storage-driver": "overlay2",
"insecure-registries":["10.107.252.139:5000"]
}

The push for the simpleapp hangs in the middle of the push

The push refers to repository [10.107.252.139:5000/tagtest]
a4399aeb9a0e: Pushed
35a91a75d24b: Pushed
ad44aa179b33: Pushing 1.011MB
2ce3c188c38d: Preparing

Any tips on how to diagnose?

Docker 19.03.6
OS 18.04
K8S 1.18.1

The final log messages displayed by journalctl -u docker.service are:

Sep 03 11:18:05 vbub01a dockerd[2573]: time="2020-09-03T11:18:05.289038252-07:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Sep 03 11:18:13 vbub01a dockerd[2573]: time="2020-09-03T11:18:13.072999300-07:00" level=warning msg="Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap."
Sep 03 11:23:26 vbub01a dockerd[2573]: time="2020-09-03T11:23:26.398379723-07:00" level=info msg="Attempting next endpoint for push after error: Get https://10.107.252.139:5000/v2/: http: server gave HTTP response to HTTPS client"

Comments

  • serewicz
    serewicz Posts: 1,000
    Options

    Hello,

    There may be a few things going on. First off you should have a single line in your /etc/docker/daemon.json file, where did the extra come from? That file usually would not yet exist. What environment are you using for the labs, GCE? The lab says to create the file with one line, of course your IP may be different, something like:

    "insecure-registries":["10.107.252.139:5000"]

    After you remove the rest and restart docker does it work?

    Regards,

Categories

Upcoming Training