Docker network host need to expose4/1/2024 ![]() ![]() Are you currently working around the issue? With docker run -network=host, this could be accomplished by just using the same network schema as localhost. The user will not know these ports before starting the container, so it's not possible for the user to run the container with docker run -p. During a network penetration test, the user may be testing outbound firewall rules and needs to dynamically accept connections on different ports in the container, eg 53, 80, 443, 1337, 9001, or any other arbitary port. Making a docker container with dynamic port mappings is not possible right now.įor example, a container that allows a user to accept connections on arbitrary ports through a netcat listener. What are you trying to do, and why is it hard? Which service(s) is this request for?ĭocker Desktop for Mac, Docker Desktop for Windows Tell us about the problem you're trying to solve. The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server. Right now, docker run -network host is only available to Linux docker hosts. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |