hello again,
Now I can launch instances in nova using the docker images I uploaded. The
problem is that none of this containers is working. In the console it's
said that the instances are runing but when I try to access the console I
got those messages displayed . If do have any idea that may help me , i'm
ready to try it. By the way, when I start normal vms and not containers ,
the VM starts normally without problem and I can ping it and do everything.
[image: Images intégrées 1]
2014-09-08 13:11 GMT+02:00 ICHIBA Sara <ichi.sara(a)gmail.com>:
Thank you Kashyap for your response,
in order to configure docker to use the proxy , I found that we should set
the proxy's variables into the file /etc/sysconfig/docker
export HTTP_PROXY="http://<proxy_host>:<proxy_port>"
export HTTPS_PROXY="http://<proxy_host>:<proxy_port>"
once i did this , the two commands worked just fine.
2014-09-08 12:29 GMT+02:00 Kashyap Chamarthy <kchamart(a)redhat.com>:
> On Mon, Sep 08, 2014 at 10:26:48AM +0200, ICHIBA Sara wrote:
> > Hey guys,
> >
> > I have installed an all-in-one openstack vm using packstack. Now i'm
> > trying to install docker and get nova use it.
> >
> > I'm following this tuto
https://wiki.openstack.org/wiki/Docker. When I
> > try the docker search or the docker pull samalba/hipache commandes it
> > gives me this error :2014/09/08 12:02:07 Get
> >
https://index.docker.io/v1/repositories/samalba/hipache/images: dial
> > tcp 162.242.195.84:443: connection timed out .
> >
> > I think it's because of the proxy. Have anywone any idea on where I
> > can set the proxy variable for the docker to use it?
>
> I'm not a Docker user, but just a related comment: Lars has written[1] a
> couple of blogposts related to Nova/Docker and Heat, where he talks[2]
> about configuring Docker to listen on a TCP socket:
>
>
> [1]
http://blog.oddbit.com/2014/08/28/novadocker-and-environment-var/
> [2]
http://blog.oddbit.com/2014/08/30/docker-plugin-for-openstack-he/
>
>
> Hope that helps.
>
> --
> /kashyap
>