title: Bluemix Container status reads 'Networking'
body: <p>I am attempting to setup a container on Bluemix that accepts UDP traffic and forwards it using a TCP connection to Logentries. When running the container locally, I used NetCat to simulate UDP traffic and saw it successfully displayed at the destination of the TCP connection.</p>
  
  <p>However, when I attempt to start a container based off the same image with Bluemix containers service, the container remains stuck in a 'Networking' state and no data is transmitted to the destination. The logs only print a warning about the version listed in the syslog-ng.conf file (same warning when ran locally), and inspection of the container by command <code>cf ic inspect &lt;container-id&gt;</code> returns the following portion about the <code>Networking</code> state:</p>
  
  <pre><code>"Path": "date",
  "ResolvConfPath": "/etc/resolv.conf",
  "State": {
      "ExitCode": 0,
      "FinishedAt": "0001-01-01T00:00:00Z",
      "Ghost": "",
      "Pid": 1,
      "Running": true,
      "StartedAt": "2015-10-14T19:45:43.000000000Z",
      "Status": "Networking"
  },
  </code></pre>
  
  <p>One thing to note is that I had to change the nameserver to <code>8.8.8.8</code> (Google's DNS) for necessary domain name resolution, due to the following error:</p>
  
  <pre><code>Error resolving hostname; host='data.logentries.com'
  Error initializing message pipeline;
  Error resolving hostname; host='data.logentries.com'
  Error initializing message pipeline;
  </code></pre>
  
  <p>You can find the source code of the Docker image I originally adopted at <code>https://github.com/oinopion/syslog-ng-logentries</code>.</p>
  
  <p>So my questions are:</p>
  
  <ol>
  <li>What does the 'Networking' state of a Bluemix container mean?</li>
  <li>Why does my container work locally but not on Bluemix? </li>
  </ol>