OpenEMR 5.0.1 in VM appliance with recommended resources takes longer to bind a socket to :80/:443

Situation
Trying out OpenEMR 5.0.1 in a VM form factor running within VMware workstation and I am running into a strange issue.

I’ve downloaded the OVA from openemr-devops/packages/appliance at master · openemr/openemr-devops · GitHub

In one of my VM’s I see the VM has an IP address that is pingable but there is no ‘docker-pr’ service that is bound as a socket to http/https.

In another VM I see the docker-pr service bound successfully and the portal works fine.

See screenshot

The changes I made to the VM properties are
a) increase swap to 2gb
b) increase disk to 100gb (vs 10gb default)
c) increase ram to 2gb
d) increase CPU cores to 2

Note: If I wait for approximately 15 minutes of VM uptime, the docker-pr service on the ‘not working’ VM does come up automatically (no user intervention).

I am not sure what is causing it to take 15 minutes longer when it has more resources allocated :slight_smile:

OpenEMR Version
I’m using OpenEMR version 5.0.1

Browser:
I’m using: Firefox 62 / Chrome 69

Operating System
I’m using: Mac OSX 10.13.5 / Vmware Fusion 10.1.2 / Ubuntu 16.0.4 packaged with the OpenEMR appliance in the github link above.

Logs
I am not sure what logs to check for the ‘docker-pr’ service and was hoping someone could provide pointers as to where I should check.

Thanks a ton!!