You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was hoping to request some better documentation on how we can link/connect with containers outside Laradock since I feel it's a pretty common use-case for web apps.
Example:
I have a REST API hosted in another container. I have my laravel app using Laradock as another container.
I want to link them together so they can communicate and the Laravel container can grab the hostname of the REST container via .env service name and send requests to it.
I've managed to get it working using my own barebones docker-compose file, but I can't seem to get it working with the Laradock file and I can't seem to figure out where it's going wrong since there is quite a lot to go through and I'm still fairly new to docker.
When I try it in Laradock, it just ignores the .env and doesn't substitute it for proper hostname, so it sends requests to <service_name>:443 instead of the correct hostname substitution.
EDIT:
Another example, just discovered if I do; docker-compose exec nginx bash and then ping -c 2 service_name it sends packets, but then if I try and do the same from workspace it fails with seemingly no explanation.
The text was updated successfully, but these errors were encountered:
I was hoping to request some better documentation on how we can link/connect with containers outside Laradock since I feel it's a pretty common use-case for web apps.
Example:
I have a REST API hosted in another container. I have my laravel app using Laradock as another container.
I want to link them together so they can communicate and the Laravel container can grab the hostname of the REST container via .env service name and send requests to it.
I've managed to get it working using my own barebones docker-compose file, but I can't seem to get it working with the Laradock file and I can't seem to figure out where it's going wrong since there is quite a lot to go through and I'm still fairly new to docker.
When I try it in Laradock, it just ignores the .env and doesn't substitute it for proper hostname, so it sends requests to
<service_name>:443
instead of the correct hostname substitution.EDIT:
Another example, just discovered if I do;
docker-compose exec nginx bash
and thenping -c 2 service_name
it sends packets, but then if I try and do the same from workspace it fails with seemingly no explanation.The text was updated successfully, but these errors were encountered: