Hi Dominik, yes, you are right. The adapters are running in my local environment, the rest is running in docker. "SP_BACKEND_HOST" of connect-worker-main is already set to "localhost". Unfortunately, the URL still starts with "backend". I guess that the FileService is running in the backend. So to prevent this issue I would have to change "SP_BACKEND_HOST" in the backend to my personal IP address, right?
Tim On Feb. 17 2021, at 7:31 pm, Dominik Riemer <[email protected]> wrote: > Hi Tim, > > I assume you are running the adapter container in your local dev environment? > In this case, you need to change the consul configuration value of the > backend host. You can do this from the Consul UI under port 8500, then switch > to the key value store and edit the " SP_BACKEND_HOST" variable (e.g., change > it to "localhost"). > Hope this helps! > > We'll soon change this behavior, once the StreamPipes client is ready, all > backend requests from the pipeline element containers will be routed over the > API then without having to change the hostname. > Dominik > -----Original Message----- > From: udeho <[email protected]> > Sent: Wednesday, February 17, 2021 3:31 PM > To: [email protected] > Subject: UnknownHostException when starting ImageStreamAdapter > > Hi all, > I just encountered an issue in the ImageStreamAdapter. > When starting the adapter, an UnknownHostException is thrown: > I was able to trace back the problem to the point where HTTP request for the > zip file is executed in the ZipFileImageIterator. > The URL that could not be resolved is: > http://backend:8030/streampipes-backend/api/v2/noauth/files/f98fa732-80b2-43f1-8a09-c6a6297f1887.zip > > Do you have any idea what might be causing this? > Best > Tim >
