[arvados] Unable to initialize Arvbox container

[Victor Kofia]

Hi Peter,

Thanks.

I tried running the arvbox container on Debian 9 and Docker 17.05 and it
worked. I don't have a lot of time to identify the root cause of the issues
I was having but here are the details in case anybody is curious in the
future.

Operating System: Ubuntu 16.04.3 LTS
Docker Version: 17.12.0-CE
Kernel Version: 4.10.0-42-generic
OSType: linux
Architecture: x86_64

Operating System: Linux Mint 18.1
Docker Version: 17.05.0-CE
Kernel Version: 4.4.0-103-generic
OSType: linux
Architecture: x86_64

(Arvbox does not work on the above platforms)

It might be useful to put a note on the Wiki or Github page in the meantime.

Best,

Victor

On Sat, Dec 30, 2017 at 8:50 PM, Peter Amstutz <pamstutz at veritasgenetics.com
> wrote:

> Hi Victor,
>
> So I think that what is happening is that the container is simply
> starting and then instead of initializing services, the init process
> immediately exits, so not being able to identify the ip address is
> just a side effect.
>
> I think I've seen this problem show up on another system, but I
> haven't been able to determine the cause.  For the record, it works
> for me using Debian 9 (Linux kernel 4.9) and Docker 17.05.
>
> - Peter
>
> On Thu, Dec 28, 2017 at 4:02 PM, Victor Kofia <victor.kofia at gmail.com>
> wrote:
> > Hi Peter,
> >
> > I am still puzzled by this issue. Can you give me some tips on how to
> > proceed? Here's my original email to the mailing list
> > (http://lists.arvados.org/pipermail/arvados/2017-November/000195.html).
> >
> > Running docker logs arvbox gives the following output:
> >
> > Arvados-in-a-box starting
> >
> > Note: if this is a fresh arvbox installation, it may take 10-15 minutes
> (or
> > longer) to download and
> > install dependencies. Use "arvbox log" to monitor the progress of
> specific
> > services.
> >
> > export ARVADOS_API_HOST=:8000
> >
> > As you can see the script is unable to identify a proper IP address. The
> > $localip variable is empty. I have tried digging into it and applying
> fixes
> > here and there but I'm still unable to get it to work. I've also tried
> it on
> > multiple machines.
> >
> > Can you please confirm that the arvbox currently on the master branch
> works?
> > If yes, what version of Docker are you using and what is your platform?
> >
> > Thanks,
> >
> > Victor
> >
> >
> > On Mon, Nov 27, 2017 at 12:02 PM, Peter Amstutz
> > <pamstutz at veritasgenetics.com> wrote:
> >>
> >> Hi Victor,
> >>
> >> It seems like the container is crashing out, which is wrong, because
> >> it is supposed to start up all the services with infinite retry.  I
> >> haven't seen this happen.  A couple of things to try:
> >>
> >> * "arvbox log" while the container is still running
> >> * docker log arvbox
> >>
> >> Thanks,
> >> Peter
> >>
> >> On Mon, Nov 27, 2017 at 9:46 AM, Victor Kofia <victor.kofia at gmail.com>
> >> wrote:
> >> > Hi everyone,
> >> >
> >> > I am having issues initializing the arvbox docker container. Here are
> >> > the
> >> > steps I have taken so far:
> >> >
> >> > - I cloned the git repository from
> >> > https://github.com/curoverse/arvados.git
> >> > - Changed the directory to tools/arvbox/bin
> >> > - Ran ./arvbox start localdemo
> >> >
> >> > Here is the output I get from the above command:
> >> >
> >> > arvbox
> >> > localdemo
> >> > 8e8d1d7dff53ff5af7cd33168ca77adddcdaf19ab9b1b4d4b9ab47633805c90a
> >> >
> >> > Arvados-in-a-box starting
> >> >
> >> > Note: if this is a fresh arvbox installation, it may take 10-15
> minutes
> >> > (or
> >> > longer) to download and
> >> > install dependencies. Use "arvbox log" to monitor the progress of
> >> > specific
> >> > services.
> >> >
> >> >
> >> > export ARVADOS_API_HOST=:8000
> >> >
> >> > Further, when I run docker events& on a separate window here is the
> >> > resulting output:
> >> >
> >> > 2017-11-27T09:35:15.177842122-05:00 container exec_create: cat
> >> > /var/run/localip_override
> >> > 8e8d1d7dff53ff5af7cd33168ca77adddcdaf19ab9b1b4d4b9ab47633805c90a
> >> > (image=arvados/arvbox-demo, name=arvbox)
> >> > 2017-11-27T09:35:15.178715537-05:00 container exec_start: cat
> >> > /var/run/localip_override
> >> > 8e8d1d7dff53ff5af7cd33168ca77adddcdaf19ab9b1b4d4b9ab47633805c90a
> >> > (image=arvados/arvbox-demo, name=arvbox)
> >> > 2017-11-27T09:35:16.417449386-05:00 container die
> >> > 8e8d1d7dff53ff5af7cd33168ca77adddcdaf19ab9b1b4d4b9ab47633805c90a
> >> > (exitCode=0, image=arvados/arvbox-demo, name=arvbox)
> >> > 2017-11-27T09:35:16.650681585-05:00 network disconnect
> >> > b7d333d91c735c971eea4da0b1b05574b19003c7d17641aad37bc1e898f3c3b2
> >> >
> >> > (container=8e8d1d7dff53ff5af7cd33168ca77a
> dddcdaf19ab9b1b4d4b9ab47633805c90a,
> >> > name=bridge, type=bridge)
> >> >
> >> > How can I fix this?
> >> >
> >> > Thanks,
> >> >
> >> > Victor
> >> >
> >> > _______________________________________________
> >> > arvados mailing list
> >> > arvados at arvados.org
> >> > http://lists.arvados.org/mailman/listinfo/arvados
> >> >
> >>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.arvados.org/pipermail/arvados/attachments/20180102/2c9c30a7/attachment.html>