I shouldn't be able to connect with the outside world from within testcon (that happens and is □), although the outside world should be able to connect testcon's port 80, and in such cases it should be able to answer the call. docker container run -name testcon -net testnet -dp 127.0.0.1:80:80 stackatoapps/phpinfoĬannot browse Describe the results you expected:.docker network create testnet -internal.However, if I publish with -p 127.0.0.1:80:80 to be able to browse that app in I simply cannot. It's very useful to avoid the inner processes contacting outside world and sending/receiving emails, etc. I have a development environment which imitates the production one but uses an -internal network. When using an -internal network, the container does not expose the requested ports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |