Using curl by default will return the response of a request as-is. If the response is a redirect, you can tell curl to follow the redirect with the -L option, e.g.
curl -L http://some.site
To use curl to download a file, use the -O option.
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.
Downloading Proxmox Container images
Before you can create a LXC container on a Proxmox virtualized environment, you need to download the template images first from an available list. You need to pre-download the images first befoe you can create new containers from them in the web ui.
From the docs here, there steps are (while ssh’d into your Proxmox server):
Update catalog of available templates:
pveam update
List the available templates:
root@pve:~# pveam available system alpine-3.3-default_20160427_amd64.tar.xz system alpine-3.4-default_20161206_amd64.tar.xz system alpine-3.5-default_20170504_amd64.tar.xz system archlinux-base_20170704-1_amd64.tar.gz system centos-6-default_20161207_amd64.tar.xz system centos-7-default_20170504_amd64.tar.xz system debian-6.0-standard_6.0-7_amd64.tar.gz system debian-7.0-standard_7.11-1_amd64.tar.gz system debian-8.0-standard_8.7-1_amd64.tar.gz system debian-9.0-standard_9.0-2_amd64.tar.gz system fedora-24-default_20161207_amd64.tar.xz system fedora-25-default_20170316_amd64.tar.xz system gentoo-current-default_20170503_amd64.tar.xz system opensuse-42.2-default_20170406_amd64.tar.xz system ubuntu-12.04-standard_12.04-1_amd64.tar.gz system ubuntu-14.04-standard_14.04-1_amd64.tar.gz system ubuntu-16.04-standard_16.04-1_amd64.tar.gz system ubuntu-16.10-standard_16.10-1_amd64.tar.gz system ubuntu-17.04-standard_17.04-1_amd64.tar.gz
For each of the templates you wish to use, download using for example for Ubuntu 14.04:
pveam download local ubuntu-14.04-standard_14.04-1_amd64.tar.gz
Now from the web ui, you should be able to click the ‘Create CT’ button and pick from your available templates:
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!