Not sure about the current English version of Eclipse Oxygen. Do you want to exit the Eclipse? I’m not sure. Do I?
Eclipse Neon:
Eclipse Oxygen:
Running a remote Docker Registry and getting ‘HTTP response to HTTPS request’ error on push
It’s been a while since I looked into running a Docker Registry to host images, my previous notes on setting this up are here. While looking into setting up Docker Registry running on a remote CentOS VM (currently running on my Mac Pro running Proxmox) I ran into the configuration issue with insecure registries.
Having tagged an image ready to push to my remote Repository, this error looks like this:
$ docker push 192.168.1.73:5000/redisservice The push refers to a repository [192.168.1.73:5000/redisservice] Get https://192.168.1.73:5000/v2/: http: server gave HTTP response to HTTPS client
Unless you’re familiar with this error and the required flag to configure running a Repository insecure (for local testing), there’s articles and posts about how to configure this, but it’s not immediately obvious that the config need to be made on the client side where you’re trying to push from, not on the server side running the Repository.
On my CentOS server side this would be configured in /etc/docker/daemon.json as:
{ "insecure-registries": [ "192.168.1.73:5000" ] }
But after finding this has no effect, I saw this post, which suggested to configure this from the client. From my Mac Docker client this can be configured using the widget in the toolbar when Docker is running:
Now trying again:
$ docker push 192.168.1.73:5000/redisservice
The push refers to a repository [192.168.1.73:5000/redisservice] 2ac8b2b0781d: Pushed 7ce27e37c9b1: Pushed e870224c1375: Pushed 3fc666989c1d: Pushed latest: digest: sha256:9f015c8d73c814d8bf0c0d089b8960c7c5c36cec750c81e09378cd2cb8d844af size: 1159
Success! Next up, I’m looking into creating a Stack of my related Container services on Rancher.
Looking up ip address in a CentOS 7 minimal install
In a minimal CentOS 7 install, there’s no ifconfig to check your network settings. Instead use
ip addr
More info here.
Error starting Openshift Origin on CentOS 7: systemd cgroup driver vs cgroupfs driver
Following the instructions to install the Openshift Origin binary from here, on first attempt to start it up I got this error:
failed to run Kubelet: failed to create kubelet:
misconfiguration: kubelet cgroup driver: "systemd" is different from docker cgroup driver: "cgroupfs"
Per instructions in this issue ticket, to verify which cgroup drivers docker is using I used:
$ sudo docker info |grep -i cgroup Cgroup Driver: cgroupfs
Unfortunately the steps to check the cgroup driver for kubernetes don’t match with my install because I’m guessing the single binary Openshift Origin has it packaged all in one, so there is no corresponding systemd config for it.
This article suggested to configure the cgroups driver for Docker so it matches kubernetes, but it looks like the yum install for docker-ce doesn’t configure systemd for it either.
Ok, to the docs. Per the Docker docs for configuring systemd here, it suggests to pull to preconfigured files from a git repo and place them in /etc/systemd/system
Now I have the systemd files for Docker in place, this articles says to add this arg to the end of the ExecStart line in docker.service:
--exec-opt native.cgroupdriver=systemdNow reload my config and restart the docker service:
sudo systemctl daemon-reload sudo systemctl restart docker
and let’s check again what cgroups driver we’re using with:
$ sudo docker info |grep -i cgroup Cgroup Driver: systemd
… and now we’ve switched to systemd.
Ok, starting up Openshift again, this issue is resolved, there’s a lot of log output as the server starts up. After opening up the firewall ports for 8443, my Openshift Console is now up!