le bac à sable de Pierre

On Linux you can access your running Docker container on localhost or remotely by publishing the desired port. On macOS it will only give you access to the Docker container from the Docker-Machine it is running on, i.e. from docker-machine ip <machine_name> . To access it on localhost, you can use ssh port forwarding: docker-machine ssh <machine_name> -fNTL <local_port> :localhost:<machine_port> You can now access your Docker container on localhost:<local_port> . Bonus: Accessing your Docker container from a remote computer. By default, with ssh -L , the local port is bound for local use only. You can use the bind _address option to make your Docker container available publicly: docker-machine ssh <machine_name> -fNTL \*:<local_port>:<localhost>:<machine_port> You can now access your Docker container on <your_ip>:<local_port> .

Unzipping files recently stopped working on my MacBook Air running OSX Mountain Lion. I found the solution to my problem on StackExchange: execute the following command in a Terminal: sudo killall -KILL appleeventsd Other symptoms / problems solved by this command: Opening downloaded files from Chrome is not working "Show in Finder" is not working Alternatively, you can kill the appleeventsd process in Activity Monitor: Source:  http://apple.stackexchange.com/questions/70160/can-i-fix-things-so-archive-utility-doesnt-hang-on-all-zip-files