PR idea for running tklx.org/base-based container with networking

[elimisteve]

Would you accept a PR recommending that, if people want network connectivity from within a tklx.org/base-based rkt container, that they should run

sudo rkt run tklx.org/base:0.1.1 --interactive --exec /bin/bash --volume resolv,kind=host,source=/etc/resolv.conf,readOnly=true --mount volume=resolv,target=/etc/resolv.conf --net=host

rather than merely

sudo rkt run tklx.org/base:0.1.1 --interactive --exec /bin/bash

? Thanks!

[elimisteve]

Just mounting /etc/resolv.conf, and just setting --net=host, both result in DNS issues for me:

root@rkt-533d64f4-6fac-4849-9639-014eff309b55 /# apt-get update
Err http://security.debian.org jessie/updates InRelease
  
Err http://httpredir.debian.org jessie InRelease
  
Err http://httpredir.debian.org jessie Release.gpg
  Could not resolve 'httpredir.debian.org'
Err http://security.debian.org jessie/updates Release.gpg
  Could not resolve 'security.debian.org'
Reading package lists... Done
W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease  

W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie/InRelease  

W: Failed to fetch http://security.debian.org/dists/jessie/updates/Release.gpg  Could not resolve 'security.debian.org'

W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie/Release.gpg  Could not resolve 'httpredir.debian.org'

W: Some index files failed to download. They have been ignored, or old ones used instead.

[JedMeister]

Hi @elimisteve thanks for your input. TBH I'm not really up to speed with TKLX so can't really comment myself.

@qrntz ?