{"push_id":952271695,"size":1,"distinct_size":1,"ref":"refs/heads/alban/dns-2","head":"53d45473ba5601fe37fe866c805d3f8a97d043c5","before":"560e71ed3abc5c7892a0e3c36936acb304a0b476","commits":[{"sha":"53d45473ba5601fe37fe866c805d3f8a97d043c5","author":{"email":"5d61c11e6df8ed8ffd2a3627a86b97e825765970@kinvolk.io","name":"Alban Crequy"},"message":"*: fill resolv.conf from command line\n\nrkt now provides /etc/resolv.conf in each app's chroot.\n\nGetting DNS information from the CNI or from the host's resolv.conf is\nout of scope of this patch. The content of /etc/resolv.conf comes from\nthe command line parameters:\n- \"--dns=\": comma-separated list\n\nImplementation detail: systemd-nspawn can overwrite /etc/resolv.conf. It\nis supposed to overwrite it only when the container uses the host\nnetwork namespace.  However, the container network namespace is created\nby rkt via CNI and not by systemd-nspawn, so systemd-nspawn is not aware\nof the network configuration. As a consequence, we cannot use stage1's\n/etc/resolv.conf. Instead, rkt write /etc/rkt-resolv.conf in stage1 and\nprepare-app bind-mounts it in stage2's /etc/resolv.conf.\n\nIt works in this way:\n\n> $ sudo rkt run --net=alban --dns=1.1.1.1,2.2.2.2 \\\n> \t\tsha512-a2fb8f390702 --interactive\n> / # cat /etc/resolv.conf\n> # Generated by rkt\n>\n> # Name servers passed on the command line\n> nameserver 1.1.1.1\n> nameserver 2.2.2.2\n> / #\n\nFixes https://github.com/coreos/rkt/issues/660","distinct":true,"url":"https://api.github.com/repos/kinvolk/rkt/commits/53d45473ba5601fe37fe866c805d3f8a97d043c5"}]}