https://linen.dev logo
Join Slack
Powered by
This message was deleted.
# opal
s
This message was deleted.
r
How are you trying to communicate with it ?
So the fetcher is on your local machine, and the opal-server is on docker ?
a
both are built as docker containers running on my machine
oh localhost on the client is not localhost on my machine
right?
r
I’m not sure what do you mean
but what is the host that you are giving to the fetcher ?
a
the client docker container can’t reach the server container
I think it’s defaulting to localhost:7002 for the server
o
If OPAL-client fails to reach the OPAL-server - that is a lot before the fetcher comes into the picture. Were you able to run this docker compose setup before?
a
No I haven’t got it working yet.
o
Probably some docker/networking issues Consider starting with our vanilla docker compose example , and once’s that’s live adding on top. often 
docker.internal.host
instead of 
localhost
is an issue
👀 1
a
Have you run into the issue where you can’t start opal client without changing port 7000? MacOS afs3-fileserver binds to the port on boot.
o
Yeah, that can happen, but you can map docker to another port, in Permit's PDP we do that by default
a
cool! Yeah I think I’ve got the docker-compose setup working. I think… now it’s just a matter of configuring the ENV var for 
DATA_CONFIG_SOURCES
. Kind of a process to get here, but not bad as far as custom plug-ins go
o
Yeyy 💪. And yeah data_config_sources is your next step. Always happy to hear feedback/ ideas on improving the experience
Open in Slack
PreviousNext
Powered by