Sometimes, Docker’s usual http://1.2.3.4:8080 syntax is just fine for localdev. Othertimes, it’s not. Let’s explore when you’ll need to change things up, why you need to do so, and how to easily achieve the next step up: https-enabled domain names for your local environments.
Opening up the Docker socket to a container results in the possibility that someone can utilize that container to break into the host machine. This is an example showing how to prevent such a jailbreak - it uses a localdev stack, though the solution for the socket used can also be used in a production environment.
This fixes issues with Docker container volumes on Linux. If this fix is not put in place, files and directories created and edited within the container may show up on the host machine with unwritable/unreadable permissions. OSX and Windows users do not need to worry about this, since Docker runs ontop a VM in those operating systems and the permissions are handled by Docker and that VM.