Docker Containerized execution on local system: Error connectivity between DSS and container

galghaith

Hi,

I'm trying to setup "Containerized execution" using Docker. I've installed docker desktop then ran the following command:

./bin/dssadmin build-base-image --type container-exec

When I test the docker I get an error related to connectivity between DSS and container. How can I fix this issue?

 

 

Error:

Starting Docker container
Installing debugging signal handler
[2022-10-27 07:21:16,210] [1/MainThread] [INFO] [root] Fetching job definition
[2022-10-27 07:21:16,210] [1/MainThread] [DEBUG] [root] Verifying SSL calls with certificate True
[2022-10-27 07:21:16,210] [1/MainThread] [DEBUG] [root] Verifying SSL calls with certificate True
[2022-10-27 07:21:16,210] [1/MainThread] [DEBUG] [root] Verifying SSL calls with certificate True
[2022-10-27 07:21:16,210] [1/MainThread] [DEBUG] [root] Verifying SSL calls with certificate True
[2022-10-27 07:21:16,212] [1/MainThread] [DEBUG] [urllib3.connectionpool] Starting new HTTP connection (1): slb-3qn43m3:12001
[2022-10-27 07:21:16,215] [1/MainThread] [ERROR] [root] Could not reach DSS: HTTPConnectionPool(host='slb-3qn43m3', port=12001): Max retries exceeded with url: /dip/api/tintercom/containers/get-execution (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f75dae8e7b8>: Failed to establish a new connection: [Errno -2] Name or service not known',))

---

Operating system used: Centos

---

Operating system used: Centos

Turribeach

Sounds like your container is not able to DNS resolve your hostname. This might help:

https://stackoverflow.com/questions/62968807/dns-resolution-in-docker-containers

galghaith

I edited /etc/docker/daemon.json file and added

{
"dns": ["8.8.8.8"]
}

Restarted Docker then tested Containerized execution again and got the same error.

I also tested changed Docker network field (from Dataiku containerized execution config page) to host and bridge and still didn't work.

matthieu

The docker container is trying to connect to the hostname slb-3qn42m3 which is locally significat to your setup and might not be known by your container running on docker for windows.

Make sure to configure the DKU_BACKEND_EXT_HOST as described in https://doc.dataiku.com/dss/latest/containers/troubleshooting.html The IP or URL configured there will be used by the container to reach back the DSS instance