LXD on Manual incorrect resolv.conf

[Tom Barber]

Hi folks,

I’m trying to do a manual cloud with LXD containers within it.

When I manually launch and LXD container I get

nameserver 10.61.251.1
search lxd

If juju launches a container it gets:

nameserver 127.0.0.1
search ovh.net lxd

Which doesn’t connect to the interwebs and makes Juju sad. What can I do to
fix this?
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.




All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.

[Tim Penhey]

Hi Tom,

What is your expectation on how the containers are getting their IP
addresses?

Also, which version of Juju?

Tim

Post by Tom Barber
Hi folks,
I’m trying to do a manual cloud with LXD containers within it.
When I manually launch and LXD container I get 
nameserver 10.61.251.1
search lxd
nameserver 127.0.0.1
search ovh.net <http://ovh.net> lxd
Which doesn’t connect to the interwebs and makes Juju sad. What can I do
to fix this?
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

[Tom Barber]

I don’t have any expectation other than connectivity to the internet would
be nice because otherwise it makes juju quite hard :)

But irrespective of my expectations, if standalone LXD containers get a
resolv.conf that allows connection to the WWW, why doesn’t Juju, it seems
both reasonable and logical? I guess thats my expectation, considering the
containers need to apt-get etc.

Juju is 2.3.7

Tom


On 26 June 2018 at 21:57:21, Tim Penhey (***@canonical.com) wrote:

Hi Tom,

What is your expectation on how the containers are getting their IP
addresses?

Also, which version of Juju?

Tim

Post by Tom Barber
Hi folks,
I’m trying to do a manual cloud with LXD containers within it.
When I manually launch and LXD container I get
nameserver 10.61.251.1
search lxd
nameserver 127.0.0.1
search ovh.net <http://ovh.net> lxd
Which doesn’t connect to the interwebs and makes Juju sad. What can I do
to fix this?
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Juju mailing list
***@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.




All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.

[Tim Penhey]

I guess I should have been more clear with respect to the IP addresses.

Clearly the container isn't being set up correctly if it can't reach out
and we should look into that.

When a container is started there are several options for how it gets an
IP address. The various default behaviours are different for different
providers.
* there is the LXD default, which is to get an IP address from the
bridge subnet, and this container should be able to reach out, but
ingress to the container is limited to other things on the bridge.
* getting an IP address from a DHCP server
* using the fan


Tim

I don’t have any expectation other than connectivity to the internet
would be nice because otherwise it makes juju quite hard :)
But irrespective of my expectations, if standalone LXD containers get a
resolv.conf that allows connection to the WWW, why doesn’t Juju, it
seems both reasonable and logical? I guess thats my expectation,
considering the containers need to apt-get etc.
Juju is 2.3.7
Tom

Post by Tim Penhey
Hi Tom,
What is your expectation on how the containers are getting their IP
addresses?
Also, which version of Juju?
Tim

Post by Tom Barber
Hi folks,
I’m trying to do a manual cloud with LXD containers within it.
When I manually launch and LXD container I get 
nameserver 10.61.251.1
search lxd
nameserver 127.0.0.1
search ovh.net <http://ovh.net> <http://ovh.net> lxd
Which doesn’t connect to the interwebs and makes Juju sad. What can I do
to fix this?
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju

09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

[Tom Barber]

Ah right, apologies, the IP address is provided by the LXD default bridge.


On 26 June 2018 at 22:31:12, Tim Penhey (***@canonical.com) wrote:

I guess I should have been more clear with respect to the IP addresses.

Clearly the container isn't being set up correctly if it can't reach out
and we should look into that.

When a container is started there are several options for how it gets an
IP address. The various default behaviours are different for different
providers.
* there is the LXD default, which is to get an IP address from the
bridge subnet, and this container should be able to reach out, but
ingress to the container is limited to other things on the bridge.
* getting an IP address from a DHCP server
* using the fan


Tim

Post by Tom Barber
I don’t have any expectation other than connectivity to the internet
would be nice because otherwise it makes juju quite hard :)
But irrespective of my expectations, if standalone LXD containers get a
resolv.conf that allows connection to the WWW, why doesn’t Juju, it
seems both reasonable and logical? I guess thats my expectation,
considering the containers need to apt-get etc.
Juju is 2.3.7
Tom

Post by Tim Penhey
Hi Tom,
What is your expectation on how the containers are getting their IP
addresses?
Also, which version of Juju?
Tim

Post by Tom Barber
Hi folks,
I’m trying to do a manual cloud with LXD containers within it.
When I manually launch and LXD container I get
nameserver 10.61.251.1
search lxd
nameserver 127.0.0.1
search ovh.net <http://ovh.net> <http://ovh.net> lxd
Which doesn’t connect to the interwebs and makes Juju sad. What can I do
to fix this?
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju

09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.




All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.

[Tim Penhey]

Am I right in assuming that you are bringing up bionic containers?

Post by Tom Barber
Ah right, apologies, the IP address is provided by the LXD default bridge.

Post by Tim Penhey
I guess I should have been more clear with respect to the IP addresses.
Clearly the container isn't being set up correctly if it can't reach out
and we should look into that.
When a container is started there are several options for how it gets an
IP address. The various default behaviours are different for different
providers.
* there is the LXD default, which is to get an IP address from the
bridge subnet, and this container should be able to reach out, but
ingress to the container is limited to other things on the bridge.
* getting an IP address from a DHCP server
* using the fan
Tim

I don’t have any expectation other than connectivity to the internet
would be nice because otherwise it makes juju quite hard :)
But irrespective of my expectations, if standalone LXD containers get a
resolv.conf that allows connection to the WWW, why doesn’t Juju, it
seems both reasonable and logical? I guess thats my expectation,
considering the containers need to apt-get etc.
Juju is 2.3.7
Tom

Post by Tim Penhey
Hi Tom,
What is your expectation on how the containers are getting their IP
addresses?
Also, which version of Juju?
Tim

Post by Tom Barber
Hi folks,
I’m trying to do a manual cloud with LXD containers within it.
When I manually launch and LXD container I get 
nameserver 10.61.251.1
search lxd
nameserver 127.0.0.1
search ovh.net <http://ovh.net> <http://ovh.net> <http://ovh.net> lxd
Which doesn’t connect to the interwebs and makes Juju sad. What can I do
to fix this?
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju

09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

[Tom Barber]

So
. Rick said there was a LP bug about bionic containers I looked at which
vaguely looked similar. But alas, they are all Xenial.

Basically as a starter for 10, I launched a Xenial host, added it to my
controller, deployed Mattermost and Postgres to containers on it, both
Xenial, and neither could talk to the internet so neither installed.
Adjusted the resolv.conf and they then installed, but then the resolv gets
zapped so they stop talking.




On 26 June 2018 at 23:39:15, Tim Penhey (***@canonical.com) wrote:

Am I right in assuming that you are bringing up bionic containers?

Post by Tom Barber
Ah right, apologies, the IP address is provided by the LXD default bridge.

Post by Tim Penhey
I guess I should have been more clear with respect to the IP addresses.
Clearly the container isn't being set up correctly if it can't reach out
and we should look into that.
When a container is started there are several options for how it gets an
IP address. The various default behaviours are different for different
providers.
* there is the LXD default, which is to get an IP address from the
bridge subnet, and this container should be able to reach out, but
ingress to the container is limited to other things on the bridge.
* getting an IP address from a DHCP server
* using the fan
Tim

Post by Tom Barber
I don’t have any expectation other than connectivity to the internet
would be nice because otherwise it makes juju quite hard :)
But irrespective of my expectations, if standalone LXD containers get a
resolv.conf that allows connection to the WWW, why doesn’t Juju, it
seems both reasonable and logical? I guess thats my expectation,
considering the containers need to apt-get etc.
Juju is 2.3.7
Tom

Post by Tim Penhey
Hi Tom,
What is your expectation on how the containers are getting their IP
addresses?
Also, which version of Juju?
Tim

Post by Tom Barber
Hi folks,
I’m trying to do a manual cloud with LXD containers within it.
When I manually launch and LXD container I get
nameserver 10.61.251.1
search lxd
nameserver 127.0.0.1
search ovh.net <http://ovh.net> <http://ovh.net> <http://ovh.net> lxd
Which doesn’t connect to the interwebs and makes Juju sad. What can I do
to fix this?
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is

confidential,

Post by Tom Barber

Post by Tim Penhey

Post by Tom Barber

Post by Tim Penhey

Post by Tom Barber
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju

09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.

--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.




All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.