Set community edition via docker on a virtual CentOS box

There's quite a few factors to consider here.
Where is this virtual centOS hosted and how is the network configured?

On the virtual centos, do you have something like FirewallD running that needs to open up the ports there as well?

have you confirmed the siemplify service is running? Dead service won't return syn/ack

The device is network accessible, virtualized on a type 1 hypervisor on a base CentOS 7. I have run tcpdump on the instance and can confirm the SYN packets hit it. It's bridged with a dedicated IP mapped on the network side, not a 'static' configuration on the OS itself.

as best i can tell, it is running. I am not very familiar with docker and as of this moment, I have not been able to check service status for siemplify... but the server is listening on the defined ports and i've added an any any rule to ensure the FW isn't an issue:
[root@siemplify init.d]# netstat -a|grep LISTEN|grep -v LISTENING
tcp 0 0 0.0.0.0:http 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:https 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:esmagent 0.0.0.0:* LISTEN
tcp6 0 0 [::]:http [::]:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
tcp6 0 0 localhost:smtp [::]:* LISTEN
tcp6 0 0 [::]:https [::]:* LISTEN
tcp6 0 0 [::]:esmagent [::]:* LISTEN
[root@siemplify init.d]# ps -aux|grep siem
26 29998 0.0 0.0 732704 7596 ? Ss 14:57 0:00 postgres: sa siemplify_metadata_db 127.0.0.1(46495) idle
26 30161 0.0 0.0 732704 7596 ? Ss 14:58 0:00 postgres: sa siemplify_metadata_db 127.0.0.1(46496) idle
26 30185 0.4 0.0 730732 7352 ? Ss 14:58 0:00 postgres: sa siemplify_queues_db 127.0.0.1(46497) idle
26 30187 0.0 0.0 732708 7600 ? Ss 14:58 0:00 postgres: sa siemplify_metadata_db 127.0.0.1(46498) idle
26 30196 0.0 0.0 730512 6284 ? Ss 14:58 0:00 postgres: sa siemplify_configuration_db 127.0.0.1(46499) idle
26 30202 0.0 0.0 732716 7416 ? Ss 14:58 0:00 postgres: sa siemplify_metadata_db 127.0.0.1(46500) idle
26 30203 0.0 0.0 730620 6708 ? Ss 14:58 0:00 postgres: sa siemplify_monitoring_db 127.0.0.1(46501) idle
26 30206 0.0 0.0 730756 7776 ? Ss 14:58 0:00 postgres: sa siemplify_system_db 127.0.0.1(46502) idle
26 30208 0.0 0.0 730584 6136 ? Ss 14:58 0:00 postgres: sa siemplify_jobs_db 127.0.0.1(46503) idle
26 30213 0.0 0.0 730628 6176 ? Ss 14:58 0:00 postgres: sa siemplify_report_system_db 127.0.0.1(46504) idle
26 30220 0.9 0.0 730720 7168 ? Ss 14:58 0:01 postgres: sa siemplify_queues_db 127.0.0.1(46505) idle
26 30271 0.0 0.0 730616 5996 ? Ss 14:59 0:00 postgres: sa siemplify_integrations_db 127.0.0.1(46506) idle
26 30276 0.0 0.0 730512 6284 ? Ss 14:59 0:00 postgres: sa siemplify_configuration_db 127.0.0.1(46507) idle
26 30316 0.2 0.0 730680 7428 ? Ss 14:59 0:00 postgres: sa siemplify_queues_db 127.0.0.1(46508) idle
26 30317 0.0 0.0 730512 6288 ? Ss 14:59 0:00 postgres: sa siemplify_configuration_db 127.0.0.1(46509) idle
26 30360 0.0 0.0 730512 6284 ? Ss 14:59 0:00 postgres: sa siemplify_configuration_db 127.0.0.1(46510) idle
26 30369 0.0 0.0 732724 7592 ? Ss 14:59 0:00 postgres: sa siemplify_metadata_db 127.0.0.1(46511) idle
root 30649 0.0 0.0 112820 984 pts/0 R+ 15:01 0:00 grep --color=auto siem
[root@siemplify init.d]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere

Hm. what does the command docker images show you?
and sudo docker ps -a

results of ifconfig ?

and the IP address and port you are attempting to reach the siemplify instance on?