This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 594
Docker images & port mapping. #2881
Comments
Sure, you can do something like this: {
"processes": {
"app": {
"ports": [
{
"proto": "tcp",
"port": 8000,
"service": {
"name": "myapp-web",
"create": true
}
}
]
}
}
} Which would create a service that you can then create a HTTP or TCP route for:
|
Thanks mate, much appreciated. |
How would you recommend doing this with |
@Tyler-Murphy you can use |
That works great. Thanks! |
Hi, Thanks, |
I'm also struggling to get any docker image up and running on flynn. I'm always getting the "Service Unavailable" message. running docker image locally with -p parameter works fine, but when deploying to my flynn server it never works. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have some docker images that publish web services on ports that are not 80/443. Using
docker run
, I can translate the non-standard port (8000, 8080 etc.) to 80 using the -p flag, such asdocker run -p 127.0.0.1:80:8080 ...
https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port-p-expose
Is there any way I can specify this sort of mapping in a
config.json
file?Many thanks!
The text was updated successfully, but these errors were encountered: