/Library/LaunchDaemons/de.kontextwork.docker.loopback.plist

docs

- name the file as you please, does not matter
- ensure the file is owned by root:wheel or it will not be used

It will create a loopback device 10.254.254.254 which can be used a remote_host in containers like xdebug configuration
- configure xdebug the way shown below.

Why all this?
- docker for mac will not allow to use connect_back
- you would need to use the user-specific ip of the current users interface ( eth/wlan ) in remote_host .. this way either  your bootstrap becomes utterly complex or the dev images are not portable from developer to developer

gistfile1.txt

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>de.kontextwork.docker.loopback</string>
    <key>ProgramArguments</key>
    <array>
        <string>ifconfig</string>
        <string>lo0</string>
        <string>alias</string>
        <string>10.254.254.254</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>

xdebug.ini

zend_extension=xdebug.so
xdebug.remote_autostart=0
xdebug.remote_enable=1
; this is our local loopback device we created, see /Library/LaunchDaemons/de.kontextwork.docker.loopback.plist
xdebug.remote_host="10.254.254.254"
xdebug.idekey="netbeans-xdebug"
xdebug.remote_connect_back=0
xdebug.remote_log="/tmp/xdebug.log"