Creating recipe and docker daemon not exposing my ports #410
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#410
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Where is the best place to look for how abra interacts with docker daemon? I have deployed my recipe I'm working on with abra and I can attach to the container and app is running on localhost but the daemon is not exposing the ports and when I vist app url there is no display.
Here is my compose file because you'll prolly ask for it
As you can see in the compose my app runs on port 5017 but when I
docker ps
there is no exposed port showing as there is with every other app I have deployed with abra. Not sure where the breakdown isAh @codegod100,
5017
won't be exposed to the host but will be available on theproxy
network fortreafik
to route requests from port80
/443
to. Do you havetraefik
deployed alongside your app? Treafik can be a bit of a black box but usually it will complain if it can't route your app. If you're running a localhost deployment with no requirements for TLS and such, then I think Traefik supports this but that is getting into "haven't tried this before, no idea what you'll face" mode.FYI a simple/short into guide for Traefik is https://dockerswarm.rocks/traefik/
You said
5017 won't be exposed to the host but will be available on the proxy network for treafik to route requests from port 80/443 to.
I get how this makes sense, however when I look at
docker ps
all the other apps have ports exposed so while I believe you, the anamalous behaviour is suspicious.