manageiq: appliance_console fails to start in Docker container environment

ManageIQ Virtual Appliance
To administer this appliance, browse to https://172.17.0.2
/var/www/miq/vmdb/gems/pending/appliance_console.rb:110:in `block in <module:ApplianceConsole>': undefined method `parse_conf' for #<LinuxAdmin::NetworkInterfaceGeneric:0x0055e5c8b99340> (NoMethodError)
    from /var/www/miq/vmdb/gems/pending/appliance_console.rb:106:in `loop'
    from /var/www/miq/vmdb/gems/pending/appliance_console.rb:106:in `<module:ApplianceConsole>'
    from /var/www/miq/vmdb/gems/pending/appliance_console.rb:90:in `<main>'

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 15 (15 by maintainers)

Commits related to this issue

Allow appliance_console to progress if network scripts are missing This will allow us to display network information, but not set any new configuration. Workaround for #8562 — committed to carbonin/manageiq by carbonin 8 years ago
Allow appliance_console to progress if network scripts are missing This will allow us to display network information, but not set any new configuration. Workaround for #8562 — committed to alongoldboim/manageiq by carbonin 8 years ago

Most upvoted comments

I think we’re going in the wrong direction with this… We should disable the network configuration and display features of the appliance console when run in a container. Even if you fix the issues in LinuxAdmin, you’re going to get the private container IP address (on the docker bridge), not the public IP of the host / pod where the containers services are exposed to the outside world.

bdunne on May 10, 2016