[lxc-users] Error launching first container

Discussion:

Pierre Couderc

2018-09-23 07:12:02 UTC

lxd just installed by apt on a freshly installed bionic, and after lxd
init :

lxc launch ubuntu:16.04 my-ubuntu
Creating my-ubuntu
Error: Failed container creation: Get
https://cloud-images.ubuntu.com/releases/streams/v1/index.json: lookup
cloud-images.ubuntu.com on 127.0.0.53:53: server misbehaving

I have checked that the URL
https://cloud-images.ubuntu.com/releases/streams/v1/index.json: faiils
(404) but not
https://cloud-images.ubuntu.com/releases/streams/v1/index.json (witohut
last :)

How fo I create my 1rst container ?

toshinao

2018-09-23 08:50:26 UTC

Permalink

Hi.

Your machine may be located behind firewall. In my case, even if shell’s environmental
variables such as http_proxy are properly configured, lxc tried to access 127.0.0.53.
(I am not sure wether it was 53.)

I do not to how to directly access cloud-images.ubuntu.com from behind firewall.
Here’s what I did. I prepared lxc/lxc on two locations A: a machine which has direct
internet access and B: a machine behind firewall. The goal is to launch container
on B. (1) I launched a container on A, (2) generate image of the container on A,
(3) copy the image from A to B, (4) import the image on B, (5) finally launch
container from the imported image on B.

Of course these steps are tedious and I hope there’s a better way.

Post by Pierre Couderc
lxc launch ubuntu:16.04 my-ubuntu
Creating my-ubuntu
Error: Failed container creation: Get https://cloud-images.ubuntu.com/releases/streams/v1/index.json: lookup cloud-images.ubuntu.com on 127.0.0.53:53: server misbehaving
I have checked that the URL https://cloud-images.ubuntu.com/releases/streams/v1/index.json: faiils (404) but not https://cloud-images.ubuntu.com/releases/streams/v1/index.json (witohut last :)
How fo I create my 1rst container ?
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users

Pierre Couderc

2018-09-23 17:34:44 UTC

Permalink

Thank you. I have used lxd since months but usually it was after
compiling from sources (under debian).
I have not changed anything except installing with apt under bionic
("reformatting" a computer where there was lxd under debian)
I do not imagine bionic adding a hidden firewall but I have no
experience of Ubuntu, only debian.
and 127.0.0.53, is a loopback address.

Post by toshinao
Hi.
Your machine may be located behind firewall. In my case, even if shell’s environmental
variables such as http_proxy are properly configured, lxc tried to access 127.0.0.53.
(I am not sure wether it was 53.)
I do not to how to directly access cloud-images.ubuntu.com from behind firewall.
Here’s what I did. I prepared lxc/lxc on two locations A: a machine which has direct
internet access and B: a machine behind firewall. The goal is to launch container
on B. (1) I launched a container on A, (2) generate image of the container on A,
(3) copy the image from A to B, (4) import the image on B, (5) finally launch
container from the imported image on B.
Of course these steps are tedious and I hope there’s a better way.

_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users

Andrey Repin

2018-09-23 19:30:29 UTC

Permalink

Greetings, Pierre Couderc!

Post by Pierre Couderc
lxd just installed by apt on a freshly installed bionic, and after lxd
lxc launch ubuntu:16.04 my-ubuntu
Creating my-ubuntu
Error: Failed container creation: Get
https://cloud-images.ubuntu.com/releases/streams/v1/index.json: lookup
cloud-images.ubuntu.com on 127.0.0.53:53: server misbehaving

This means that systemd-resolved did not initialize properly yet.

Post by Pierre Couderc
I have checked that the URL
https://cloud-images.ubuntu.com/releases/streams/v1/index.json: faiils
(404) but not
https://cloud-images.ubuntu.com/releases/streams/v1/index.json (witohut
last :)
How fo I create my 1rst container ?

I would check that you don't have two name resolution daemons running at once.
All too often I've seen systemd-resolved and resolvconf running in parallel,
causing all sort of trouble.
You have to select one of them and disable another, if this is your case.

--
With best regards,
Andrey Repin
Sunday, September 23, 2018 22:28:22

Sorry for my terrible english...

Pierre Couderc

2018-09-24 05:40:57 UTC

Permalink

Post by Andrey Repin
I would check that you don't have two name resolution daemons running at once.
All too often I've seen systemd-resolved and resolvconf running in parallel,
causing all sort of trouble.
You have to select one of them and disable another, if this is your case.

Thank you, I shall check that I have not 2. But what is sure is that you
are right : my name resolution does not work ! But the error meessage is
a bit mysterious...