@pollard,   Cool, I worked with Apple for a bit in 2005ish too. 🙂   To business, looks like it was Docker memory default to 2GB that was the cause.  I forgot that I noticed my container was sluggish so I bumped my Docker memory to 4GB.  I just prooved it by reverting to 2GB and then to 4GB as explained below:   Here is my session:   (1)   $ docker images REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE <none>              <none>              6d2b3c820712        19 hours ago        7GB   (2)   docker run --hostname=quickstart.cloudera --privileged=true -t -i -p 8888:8888 -p 80:80 -p 7180:7180 6d2b3c820712 /usr/bin/docker-quickstart   (3) (in container shell) # sudo -u hdfs hdfs dfs -ls / 18/09/18 16:57:09 WARN ipc.Client: Failed to connect to server: quickstart.cloudera/172.17.0.2:8020: try once and fail. java.net.ConnectException: Connection refused     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)   (4)   I log into Hue as cloudera:cloudera   Check Config shows all the failures you mentioned in your first post   (5) start over   $ exit (in the terminal launched)   * basically, kill the running container   (6)   In Docker UI configuration, Advanced:   Set Memory to 4.0GiB   Click the Apply & Restart button   (7)   Run: $ docker run --hostname=quickstart.cloudera --privileged=true -t -i -p 8888:8888 -p 80:80 -p 7180:7180 6d2b3c820712 /usr/bin/docker-quickstart   (8)   now everything works:   # sudo -u hdfs hdfs dfs -ls / Found 6 items drwxrwxrwx   - hdfs  supergroup          0 2017-10-23 23:46 /benchmarks drwxr-xr-x   - hbase supergroup          0 2018-09-18 17:06 /hbase drwxr-xr-x   - solr  solr                0 2017-10-23 23:48 /solr drwxrwxrwt   - hdfs  supergroup          0 2018-09-18 17:06 /tmp drwxr-xr-x   - hdfs  supergroup          0 2017-10-23 23:48 /user drwxr-xr-x   - hdfs  supergroup          0 2017-10-23 23:48 /var   (9)   Hue is fine... can run queries   NOTE:  the 80 and 7180 ports aren't really necessary for exposure to host OS for this test case.   I hope this solves the issue for you too! If so, it is pretty lame that lower memory would somehow let servers start and listen but then cause issues for networking to those listening ports.  I guess that is a welcome to docker for me 🙂 ... View more

@desind,   There are a few ways to enable DEBUG or TRACE depending on what sort of problem you are attempting to troubleshoot.   (1)   If CM won't start or if there is a problem where you do not have an idea what classes are involved, you can enable DEBUG or TRACE for the whole server.  Warning:  this can be very very verbose, so it is likely going to be difficult to capture an event.   - Edit /usr/sbin/cmf-server in CM 5--- Edit /opt/cloudera/cm/bin/cm-server in CM 6 - Change this: export CMF_ROOT_LOGGER="INFO,LOGFILE" to export CMF_ROOT_LOGGER="DEBUG,LOGFILE"   Restart CM to have the change apply.   (2)   If you know what class or package you want to DEBUG, you can edit /etc/cloudera-scm-server/log4j.properties:   Add lines as follows... this is an example of turning on debugging for just ldap classes in SpringFramework (used in LDAP authentication):   log4j.logger.org.springframework.ldap=TRACE log4j.logger.org.springframework.security.ldap=TRACE   Restart CM to have the changes apply   (3)   If you want to turn on some debug or trace level logging for just the current session of Cloudera Manager, you can use the debug page:   https://cm_host:cm_port/cmf/debug/logLevel   - Choose the Logger from the drop-down - Select the level to which you want to change the logging - Click "Submit Query" button to apply   The log level you selected will only apply until you restart Cloudera Manager   (4)   API debugging.   You can enable API debugging in the Cloudera Manager interface:   - Navigate to: Administration --> Settings - Search for Enable Debugging of API - Check the box next to it and Save   API debugging will be written to the /var/log/cloudra-scm-server/cloudera-scm-server.log file without restart.   (5)   NOTE:   If you do enable verbose debugging, you may need to increase the size of log files or the number to be able to review relevant lines.  To do so, I believe you can simply edit the following in /etc/cloudera-scm-server/log4j.properties:   log4j.appender.LOGFILE.MaxFileSize=10MB log4j.appender.LOGFILE.MaxBackupIndex=10     ... View more