I've been trying to customize my resolv.conf using this Dockerfile: FROM lexaguskov/freebsd RUN echo "nameserver 192.168.2.1" > /etc/resolv.conf I'm building it via `docker build -f Dockerfile -t yonas/freebsd .` but `docker run --rm -it yonas/freebsd cat /etc/resolv.conf` shows it's empty. I can add files to the image's filesystem, but not modify existing files from the lexaguskov/freebsd image. I've tested using FreeBSD 10.2 release and FreeBSD 11 current: FreeBSD freebsd-server1 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD fbsd11 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287930: Thu Sep 17 20:40:12 UTC 2015 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
Hi, I'm having the same error with /etc/resolv.conf, based on research it seems that the DNS settings are populated by Docker on run or build. In Linux this is configurable in /etc/default/docker with variable DOCKER_OPTS but this doesn't seem to be the case in FreeBSD (I tried to modify the rc script to export the env variable DOCKER_OPTS or even passing --dns 8.8.8.8 as parameter on docker daemon start without luck). For more info [1]. I'm going to test latest upstream version of Docker to see if that solves the issue as kvasdopil work was merged in [2]. Thanks! [1] https://docs.docker.com/engine/userguide/networking/default_network/configure-dns/ [2] https://github.com/docker/docker/pull/13542
Is this still relevant?
Reset assignee. kmoore@ has dropped maintainership in ports r434114. The port currently has no maintainer.
Assign to new recent maintainer (ports r489312)
EXPIRATION_DATE= 2019-09-04.
Closing PR, port is expired but not removed yet and no submitter feedback since 2016.