doc: Update cockpit/ws documentation

* Project Atomic was superseded by Fedora CoreOS.
 * It's not a "docker" container, it's just a container.
 * Speaking about "the default" is misleading, as the container isn't
   installed by default. But we only support the container there, not
   trying to squeeze the web server into an OSTree overlay.

Closes #13153
This commit is contained in:
Martin Pitt 2019-11-15 10:12:42 +01:00 committed by GitHub
parent 3769995e9f
commit 2ba0955cb6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions

View File

@ -21,9 +21,11 @@
system or you can setup a <link linkend="sso">Kerberos based SSO system or you can setup a <link linkend="sso">Kerberos based SSO
solution</link>.</para> solution</link>.</para>
<para>The web server can also be run from the <filename>cockpit/ws</filename> docker <para>The web server can also be run from the
container. If you are running cockpit on an <ulink url="https://www.projectatomic.io/"> <ulink url="https://hub.docker.com/r/cockpit/ws/">cockpit/ws</ulink>
Atomic Host</ulink> this will be the default. In this setup, cockpit establishes an container. If you are running cockpit on a container host operating system like
<ulink url="https://getfedora.org/coreos/">Fedora CoreOS</ulink>
this will be the only supported mode. In this setup, cockpit establishes an
SSH connection from the container to the underlying host, meaning that it is up to SSH connection from the container to the underlying host, meaning that it is up to
your SSH server to grant access. To login with a local account, <filename>sshd your SSH server to grant access. To login with a local account, <filename>sshd
</filename> will need to be configured to allow password based authentication. </filename> will need to be configured to allow password based authentication.