This is the fresh installed fuel master 8.0 where i cont access UI by I have tried following combinations to access fuel-master UI. https://x.x.x.x:8443 (secure PXE ip address) http://x.x.x.x:8000 (Normal PXE ip address) or https://y.y.y.y:8443 (secure public ip address) http://y.y.y.y:8000 (Normal public ip address)

[root@fuel httpd]# dockerctl list -l Name Image Status Full container name nginx fuel/nginx_8.0 Not created fuel-core-8.0-nginx rabbitmq fuel/rabbitmq_8.0 Not created fuel-core-8.0-rabbitmq astute fuel/astute_8.0 Not created fuel-core-8.0-astute rsync fuel/rsync_8.0 Not created fuel-core-8.0-rsync keystone fuel/keystone_8.0 Not created fuel-core-8.0-keystone postgres fuel/postgres_8.0 Running fuel-core-8.0-postgres rsyslog fuel/rsyslog_8.0 Not created fuel-core-8.0-rsyslog nailgun fuel/nailgun_8.0 Not created fuel-core-8.0-nailgun cobbler fuel/cobbler_8.0 Not created fuel-core-8.0-cobbler ostf fuel/ostf_8.0 Not created fuel-core-8.0-ostf mcollective fuel/mcollective_8.0 Not created fuel-core-8.0-mcollective

[root@fuel httpd]# service --status-all netconsole module not loaded Configured devices: lo eth0 eth1 Currently active devices: lo eth0 docker0 veth8d95e73 vethb73285b

Any help would be appreciated in testing Fuel 8.0

I also have issues to install fuel8 on vmware (same on xenserver 6.5). What i can get from the logs, it segfaults when generating the rabbitmq docker container. The issue you have might be the same. What do you see when you run> dockerctl list -l

bjolo