no projects configured

[urban-it-solutions]

no projects configured

[francescou]

Can you please tell me what you see in the container logs after accessing the application? Normally it should be something like this (notice the /api/v1... requests)

INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:29] "GET / HTTP/1.1" 200 -
INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:30] "GET /images/logo.png HTTP/1.1" 200 -
INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:30] "GET /styles/colors.css HTTP/1.1" 200 -
...
INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:30] "GET /scripts/services/logs.js HTTP/1.1" 200 -
INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:30] "GET /api/v1/projects HTTP/1.1" 200 -
INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:30] "GET /views/home.html HTTP/1.1" 200 -
INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:30] "GET /api/v1/host HTTP/1.1" 200 -

If your logs looks different could you please check if there are issues on the browser? (on chrome F12 -> Console).

Otherwise, can you try to execute (on a clean working copy):

docker build -t foo/docker-compose-ui .
docker run --rm -p 6000:5000 -v /var/run/docker.sock:/var/run/docker.sock foo/docker-compose-ui

and then open http://localhost:5001/#/ in your browser

Thank you.

Francesco

[urban-it-solutions]

Hi Francesco,

it´s stuck at

INFO:werkzeug:172.17.0.1 - - [06/Jan/2016 16:06:29] "GET / HTTP/1.1" 200 -

It does not work with Chrome (v 47) but with Firefox...

Thank you!

Axel

[francescou]

ok, so it's a client-side error. Could you please check the error logs on the chrome devtools console ?

[urban-it-solutions]

Now I understand! Its not a Browser problem...the application is connecting to rawgithub, cloudflare etc
I had no Internet-Connection in my Chrome-Browser...
Is it possible to integrate angular.js, css, jquery etc inside the container?

[francescou]

yes it could be done using bower.
I've created an experimental branch: "bower"

If you want to try install bower and then run:

git clone [email protected]:francescou/docker-compose-ui.git
cd docker-compose-ui
git checkout bower
(cd static/ && bower install)
docker build -t docker-compose-ui-bower .
docker run --rm -p 5003:5000 -v /var/run/docker.sock:/var/run/docker.sock docker-compose-ui-bower 

[urban-it-solutions]

great! will try that.

I have another issue...not a big thing.

Here is my compose-file:

sles12-elk-malte:
image: 172.20.132.109:5000/sles12-elk
container_name: sles12-elk-malte
cpu_shares: 1024
cpuset: 0,0
hostname: elktest
domainname: int.hlg.de
mem_limit: 2g
memswap_limit: 2g

ports:
    - "6380:6379"
    - "127.0.0.1:5602:5601"

volumes:
    - "/opt/elk/malte/conf:/conf"
    - "/opt/elk/malte/data:/data"
    - "/opt/elk/malte/logs:/logs"

But the GUI shows me:

Network

localhost:5602 : 5601/tcp

localhost:6380 : 6379/tcp

The second binding to localhost is wrong...

cheers

Axel

[francescou]

I can't see the problem here.
Internal port 6379 is published on localhost:6380, right?
Maybe your problem is that it is not an http service but, say, a redis instance?

[urban-it-solutions]

no, internal port 6379 is published to 0.0.0.0:6380....

[urban-it-solutions]

e5af8d7502dc 172.20.132.109:5000/sles12-elk "/usr/bin/supervisord" 12 seconds ago Up 10 seconds 80/tcp, 9200/tcp, 9300/tcp, 127.0.0.1:5602->5601/tcp, 0.0.0.0:6380->6379/tcp sles12-elk-malte

[francescou]

yes you're right, I've fixed the issue in 155a786
you can try the fix using the docker image francescou/docker-compose-ui:latest

[francescou]

I will close the issue, feel free to reopen if necessary.