cool, we can test it out and see. I think we must have accepted a competing pull request (I'll verify), because you can specify the net parameter in your yaml:

docker:
  net: host

@bradrydzewski sorry I might not have been clear in my original message...
I've managed to confirm this one, given the following drone.yml

---
image: library/golang:1.3
docker:
  net: host
services:
  - mysql
script:
  - env
  - echo "Hello World"
  - ip a
  - sleep 30

This results in:

Error: Failed to start build container. Internal Server Error

@dave-tucker can you give a hint, why you need a net: host for drone? We managed to get up and running Docker 1.5 with IPv6-only setup without using it.

@floatdrop we need our services and the container where the tests are run to share the same network namespace. net: host works, although using docker's --net=container:<container_name_or_id> would be much safer, but at the time of writing that functionality didn't exist in drone.

@dave-tucker I'm working on a patch that implement --net=container:{container}. Hopefully will have something to demo next week.

Without drone supporting vagrant directly, where VM's are needed (involving building VM images, testing software making use of kernel modules, alternative OS's, etc) use of --net=host seems like it would be required for vagrant inside of a container image to be able to talk to VM's launched via libvirt.

Something like https://hub.docker.com/r/twiest/docker-vagrant-libvirt/

Just evaluating drone here as a replacement, and to be able to limit the use of VM's to just the project being tested rather than needing to also bring up additional services it needs as VM's along side it would be very useful.