From 7c9785edef148a363318ef7e61b1d259082d25be Mon Sep 17 00:00:00 2001 From: spmfox Date: Wed, 3 Jul 2024 17:48:10 -0400 Subject: switching to bastion mode for cockpit-ws container, removing centos logos since cockpit-ws bastion cannot use them --- README.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index 537c0e4..72196db 100644 --- a/README.md +++ b/README.md @@ -120,5 +120,10 @@ There was some advice in that thread about using the containerized version of `` and not baked into the image. [https://quay.io/repository/cockpit/ws](https://quay.io/repository/cockpit/ws) +Using this containerized version of ```cockpit-ws``` also brought problems, using the privileged container caused mount points to be held inside the container. +This meant once the container started, ZFS datasets could not be deleted since they were still "mounted" inside the container. To workaround this bastion mode +is being used instead. That means to login to Cockpit you have to use the host ```host.containers.internal```. SSL certificates can still be added to the +```/etc/cockpit/ws-certs.d``` directory - it is mounted into the container. + This also explains why I'm using rpm vs dnf to install the 45Drives Cockpit packages - they have a dependency on ```cockpit-ws``` that I need to override. Once the official ```cockpit-files``` package is released I will be using that instead of ```cockpit-navigator```. -- cgit