There definitely appears to be something unusual on your setup that is blocking opening that port on localhost - I’ve just replicated again below. Anything at all unusual about your CentOS installs you can think of?
If anyone else is able to replicate success / failure that might also be useful. I’m afraid I’m out of ideas here as I can’t replicate the failure on a hardware CentOS install, or a VM.
dave@petroc:~/Git/singularity
03:49 PM $ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
dave@petroc:~/Git/singularity
03:47 PM $ singularity --version
2.6.0-HEAD.579c4150
dave@petroc:~/Git/singularity
Cache folder set to /home/dave/.singularity/docker
[6/6] |===================================| 100.0%
Importing: base Singularity environment
Exploding layer: sha256:8f9234435f64947bcad1104e14346b296e1b87f45a1afe2f95e3bf1cb0864926.tar.gz
Exploding layer: sha256:4768ed7b65fb84476d16e30ced8a0318191752cdf6488299dad3db72c1500cce.tar.gz
Exploding layer: sha256:315aef06947a63106f1b991c5aaf93985a3cb03c55da613fd72dac13dc85fd40.tar.gz
Exploding layer: sha256:646915aa41c68863854026530acca13cabd24e5a85f992f3532101bf70471306.tar.gz
Exploding layer: sha256:430db1c15e9318ed42284202243e072dd74e0249b333bcbc74ca908ddb168a9c.tar.gz
Exploding layer: sha256:402b231c832395be460ac7c9a55a825933cfc55ba49f3a4fd1104061f22736a1.tar.gz
Exploding layer: sha256:1980f7a9ddb8074fff5d1d18b580325882246fc86b94bc55b4fc06744a1a180b.tar.gz
WARNING: Building container as an unprivileged user. If you run this container as root
WARNING: it may be missing some functionality.
Building Singularity image...
Singularity container built: r.simg
Cleaning up...
dave@petroc:~/Git/singularity
03:49 PM $ SINGULARITY_CONTAIN=1 singularity run r.simg
R version 3.5.1 (2018-07-02) -- "Feather Spray"