[layerindex-web] Having problems instantiating a docker image

[layerindex-web] Having problems instantiating a docker image

[Mark Hatle]

I've setup the layerindex in the past (without docker).. but I'm attempting to
follow the current instructions w/o much success.

I'm trying to use:

./dockersetup.py -m 8080:80 --no-https

It asks me for my email address and then builds the docker images...

then I get a failure connecting to https://google.com, connectivity check.
Since my layerindex will never leave my network I don't care about google.. so I
re-run it with:

./dockersetup.py -m 8080:80 --no-https --no-connectivity -r

re-enter my email address, it rebuilds the docker images...

it then sits and spins with what looks like a help message for 'exec' as well as:

Database server may not be ready; will try again.


If I try to connect to that machine port 8080 with my browser, I get back a "Bad
Request (400)"

So something is running, but it's broken.

Any suggestions on getting this fixed?  Also what will the admin login be once
it DOES come alive?  I know in the past it had asked me for admin login
information and such, is the admin login documented somewhere for this docker
container?

Thanks!
--Mark

Re: [layerindex-web] Having problems instantiating a docker image

[Paul Eggleton]

Hi Mark

On Wednesday, 9 October 2019 11:59:35 AM NZDT Mark Hatle wrote:
> I've setup the layerindex in the past (without docker).. but I'm attempting to
> follow the current instructions w/o much success.
> 
> I'm trying to use:
> 
> ./dockersetup.py -m 8080:80 --no-https
> 
> It asks me for my email address and then builds the docker images...
> 
> then I get a failure connecting to https://google.com, connectivity check.
> Since my layerindex will never leave my network I don't care about google.. so I
> re-run it with:
> 
> ./dockersetup.py -m 8080:80 --no-https --no-connectivity -r
> 
> re-enter my email address, it rebuilds the docker images...
> 
> it then sits and spins with what looks like a help message for 'exec' as well as:
> 
> Database server may not be ready; will try again.

I guess that's the docker-compose version issue we talked about on IRC - if it is then I should really add a version check.

> If I try to connect to that machine port 8080 with my browser, I get back a "Bad
> Request (400)"

I wonder if something is going wrong with the -m option, since it's not something I've exercised much. Perhaps it's erroneously setting up SSL on that port? Let's see if it recurs once docker-compose is upgraded.

> So something is running, but it's broken.
> 
> Any suggestions on getting this fixed?  Also what will the admin login be once
> it DOES come alive?  I know in the past it had asked me for admin login
> information and such, is the admin login documented somewhere for this docker
> container?

The admin login for the application user is something you get to set at the end of the installation process, but you're getting stuck before that part. You can set it on the command line but there almost certainly will be other issues, so let's fix those first and then you might not have to deal with this part.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre