docs: Add installation guide for SLES

[GabyCT]

This will add the installation guide for SLES.

Fixes #85

Signed-off-by: Gabriela Cervantes [email protected]

[GabyCT]

Currently this is blocked by kata-containers/packaging#39

[chavafg]

added DNM flag as per @GabyCT request.

[jodh-intel]

• Hard-coded architecture: if this install guide only works for x86_64, this needs to be specified clearly at the top. In fact, if you added the comment and a setup section, you could you do something like:

      ```bash
      [ $(arch) != "x86_64" ] && echo ERROR: unsupported architecture && exit 1
      ```
  
  

  That would allow https://github.com/kata-containers/tests/blob/master/.ci/kata-doc-to-script.sh to do the right thing (TM) :)

• This looks fragile to me as it's manually installing an OpenSuSE package on SLES. With Clear Containers we simply installed docker - what's the reason we can no longer do that? Is the version too old?

  • https://github.com/clearcontainers/runtime/blob/master/installation/sles-setup.sh#L128

[GabyCT]

@jodh-intel , there is an issue with SLES when we installed docker with

$ zypper -n install docker

This will install docker version 17.09.1-ce, build f4ffd2511ce9. However, after doing the installation of kata-runtime, kata-proxy, etc which is done correctly and trying to do the following

$ sudo systemctl daemon-reload
$ sudo systemctl restart docker

We have the following error

-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
may 22 18:33:44 gaby-sles dockerd[20809]: time="2018-05-22T18:33:44Z" level=info msg="SUSE:secrets :: enabled"
may 22 18:33:44 gaby-sles dockerd[20809]: time="2018-05-22T18:33:44.722479100Z" level=debug msg="Listener created for HTTP on unix (/var/run/docker.sock)"
may 22 18:33:44 gaby-sles dockerd[20809]: Failed to connect to containerd. Please make sure containerd is installed in your PATH or you have specified the correct address. Got error: exec: "docker-containerd": executable file not found in $PATH
may 22 18:33:44 gaby-sles systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
may 22 18:33:44 gaby-sles systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.

Now containerd is being installed by SLES.
containerd version 0.2.3 commit: 06b9cb35161009dcb7123345749fef02f7cea8e0

And docker-containerd does not exist

$ zypper search docker*
Loading repository data...
Reading installed packages...
i+ | docker                   
    | docker                      
    | docker-distribution       
    | docker-distribution-registry 
    | docker-image-migrator  
    | docker-img-store-setup 
i   | docker-libnetwork      
i   | docker-runc                 

However, this error did not happen when I am trying to manually installed and OpenSuSE package on SLES.

[GabyCT]

This is the configuration that I am using

$ cat /etc/os-release
NAME="SLES"
VERSION="12-SP3"
VERSION_ID="12.3"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP3"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp3"

[jodh-intel]

Hi @ajaeger - do you have any input on this SLES issue?

[vrothberg]

Hi @GabyCT, @jodh-intel,

I am co-maintaing the Docker packages at SUSE and @ajaeger asked me to have a look at the SLES issue.

However, this error did not happen when I am trying to manually installed and OpenSuSE package on SLES.

Can you elaborate a bit more which setup is working and which not? In theory, a zypper install docker and systemctl start docker should always lead to a running Docker daemon on our supported systems (i..e, latest SLES and openSUSE).

And docker-containerd does not exist

That's correct as we ship it in the containerd package, both on SLES and openSUSE.

may 22 18:33:44 gaby-sles dockerd[20809]: Failed to connect to containerd. Please make sure containerd is installed in your PATH or you have specified the correct address. Got error: exec: "docker-containerd": executable file not found in $PATH

The error log shows that dockerd tries to start docker-containerd and I understand the confusion as we don't ship a docker-containerd binary but only a containerd one. The reasoning behind is that we manage our services via systemd to avoid containerd being a subprocess of dockerd. We consider this setup to a bit cleaner but it is has no functional impact.

@GabyCT If possible, could you upload the logs of docker and containerd (journalctl -u docker and journalctl -u containerd)? Can you try to start containerd (systemctl start containerd) and check if it's running (systemctl status containerd)? Did you change any systemd service files for either docker or containerd?

[vrothberg]

@GabyCT Are you using the docker and containerd packages provided by SUSE? It's just a wild guess, but maybe there were some packages left in your test environment that did not come from SUSE (i.e., zypper in docker).

[jodh-intel]

Hi @GabyCT - sorry, but I don't have a SLES license.

[GabyCT]

@vrothberg, I just did the zypper -n install docker

[GabyCT]

@chavafg could you please help me to reproduce this error? I want to see if it is something from my environment or you also hit the same error thanks

[chavafg]

@GabyCT
I tried today and I could start the docker daemon with this config:

fuentess@sles-kata:~> cat /etc/systemd/system/docker.service.d/kata-containers.conf
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -D --containerd /run/containerd/containerd.sock --add-runtime kata-runtime=/usr/bin/kata-runtime --default-runtime=kata-runtime

I think that @vrothberg approach should also work, but you'll would need to delete the /etc/systemd/system/docker.service.d/kata-containers.conf

I used the docker that is provided by SUSE. Version is: 17.09.1-ce

[chavafg]

I think we should remove the steps of adding this repo and install docker-engine. This docker version is 17.05, which is older than the one that SUSE provides, which is 17.09

[chavafg]

add --containerd /run/containerd/containerd.sock or change to use /etc/sysconfig/docker instead of the docker service config file.

[GabyCT]

@chavafg changes applied

[GabyCT]

@vrothberg the changes were applied and now docker is working thank you.

[GabyCT]

@jodh-intel , I applied all the changes that are required however this is still blocked by issue kata-containers/packaging#39

[vrothberg]

@vrothberg the changes were applied and now docker is working thank you.

That's wonderful news :) Thanks a lot, @GabyCT!

[chavafg]

@GabyCT, @jodh-intel, @egernst

about the kata-containers/packaging#39,
should we add a workaround to the document for the moment?

I know that this won't be elegant, but will allow us to have the documentation for SLES.

[jodh-intel]

Hi @chavafg - I've asked @GabyCT to comment on a possible fix on kata-containers/packaging#39. However, if we really can't get this to work I guess we could consider adding something like the following to install/sles-installation-guide.md:

$ sudo mkdir -p /usr/libexec/kata-containers
$ sudo ln -s /usr/lib64/kata-containers/kata-proxy /usr/libexec/kata-containers/kata-proxy
$ sudo ln -s /usr/lib64/kata-containers/kata-shim /usr/libexec/kata-containers/kata-shim

[GabyCT]

@jodh-intel changes applied

[jodh-intel]

Thanks @GabyCT - I think the workaround should be fine until we get a chance to update and re-test the packaging for SuSE.

[jodh-intel]

Ping @chavafg, @kata-containers/documentation.

[caoruidong]

lgtm

[bergwolf]

@chavafg PTAL.