Closed ssimsekler closed 3 years ago
Same issue faced as well: https://imgur.com/a/kyTCUdw
Same issue here as well.
Hi @sammok83, @mario-fliegner Hi @nzamani :)
please check my fork https://github.com/wozjac/sap-cloud-connector-docker. It has http configured for the connector, so after all run it using http://localhost:8443.
I don't know the internals of SAP Cloud Connector, but the "Connector" setting seems to be related only with the endpoint for the host; if yes, then unencrypted communication is only within the host computer running Docker.
The message you are receiving "Failed to get D-Bus connection: Operation not permitted" is irrelevant here, the connector is started and the end using java
Possibly someone more advanced with networking would be able to check it. There was a reported issue with JDK (SAP note 2745641), I tried the solution from it also, did not work.
Cheers, Jacek
Thanks for reporting, and to others for helping out! As @wozjac said the error you get can be ignored. Docker works with PID 1, systemd etc is not needed. Also, we don't want privileged mode.
Previous versions of my docker file used a java call. With cab892f465949a88c52212090c4e7835fe9f643c the dockerfile now uses ./go.sh instead which is shipped directly from SAP. No other tweak needed anymore. Plus the mentioned change uses the latest SAPCC 2.13.0
Hi Nabi
The docker container cannot run SCC saying "Failed to get D-Bus connection: Operation not permitted". It seems some problem around unprivileged access to systemd as per the issue reported here.
Any systemctl start/restart fails raising similar error message.
There is a similar issue raised which is fixed; however, I am still encountering the problem. BTW, I adapted the Dockerfile to use newest SAP JVM and SCC versions:
Kind Regards