With version 11 I installed and used CA jupiter notebook with RHEL 7 and docker-ce. It was easy to install and worked well.
For CA 12 I decided to go with RHEL 8 and to use Podman. Installation seems easy.

The first problem is that when launching starrtup.sh (as root) at the end I get the message "chown: cannot access '/var/run/docker.sock': Permision denied".
But the two images launch fine and when I type in the browser http://localhost:8000 (or FQDN of the server) I see a nice message: "You are connected to Cognos Analytics for Jupiter Notebnook!".
Great.
Now I'm trying to enable access from my CA server (under Windows).
I added my jupyter server in CA_IIS... script, deleted the gateway configuration in IIS and re-ran the script (IIS configuration looks good). 

Subsequently I opened the rights to the notebook to all authenticated people.
I have a blue wheel that spins for a long time and I get the message: "An unexpected error occurred.Check the Jupyter server logs.".
And there is nothing in the logs folder :(.
I don't really know how to get out of it.
The problem is related to chown on ca_user which does not work in startup?
Otherwise in config.conf there is a new parameter COGNOS_HOST.
In the documentation it is written to initialize it with the same content as "Dispatcher URI for External Application" and as an example we have http://cognos-host:9300, or in Cognos Configuration we have http://cognos-host :9300/bi/v1/disp.
The two servers ping each other. I checked the procedure and configuration several times. I don't work with SSL. Port 8000 is open on the jupyter server. CAF is off.
Has anyone ever run CA 12 (with gateway) and Jupiter on RHEL 8?

Thanks for your help

jerzy

We're running 11.2.4.1 on podman on RHEL with proxy

We had to make sure that

• hostname part of COGNOS_HOST. in config.conf and 'Jupyter service location' in system config is the same
• proxy forward rules were added: https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=cahshs-configuring-apache-http-server-http-server-cognos-analytics
• as for logs, we monitored: podman logs --follow=true  ca_jupyter_hub (e.g. we found a 'cross site scripting' error on starting the notebook server, which led to a timeout in the browser)

Does the notebook container start on trying to open/create a notebook ?

Is there any old containers left that may interfere ?

Or any sock processes  active tha t should not ?

Hi Thomas,

My CA version is 12.0.1
For the host name I use the $hostname variable which returns the same value as the one I have in the system configuration
I use Microsoft IIS and to initialize it I used the script provided by Cognos. I later checked the rules are OK
I have only CA containers. 

When I execute startup.sh at the last I have a message "chown: cannot access '/var/run/docker.sock': Permission denied" and it's very strange because I start it as root. 
With podman logs I have too somme strange "Permission denied". 

I installed the RHEL server twice for testing and both times I got the same result.

Any idea ?

We ran into a permission denied on /run/user/0/bus like this:

Starting CA Jupyter podman containers
using overridden websocket spec ws://ams4apw01ls:8000
ERRO[0000] failed to move the rootless netns slirp4netns process to the systemd user.slice: dial unix /run/user/0/bus: connect: permission denied 

Solution was this:

To allow for systemd services to be started at boot without login (and continue running after logout) of the individual users, you need to enable "lingering".  You can do that via loginctl enable-linger <username>. It's buried in the manpages of podman-generate-systemd:

http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html" title="http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html" href="http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html" rel="noreferrer noopener" target="_blank" class="fui-Link ___10kug0w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" style="overflow-wrap: break-word">http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html

No idea if that relates to your problem ...

Hi Jerzy,

were you able to solve the problem? We have run exactly into the same issue, the only difference being we run the setup on RHEL9 server. We tried to install the version 12.0.4 first and kept receiving the same error as you: "chown: cannot access '/var/run/docker.sock': Permission denied". We don't have docker installed at all and ran the install.sh as root.

Afterwards we tried to install the version 11.2.4 instead with basically the same failure. The only difference when installing v 11.2.4. is somewhat better error message saying. "chown: cannot access '/podman/podman-ca-jupyter.sock': Permission denied" which seems to be appropriate as we use podman.

So the problem seems related to podman socket and not to installation itself.

Would be great to hear if you found the reason for the failure.

Kind regards

Peter Mandzak