Bluemix Container status reads 'Networking'

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.

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 cf ic inspect <container-id> returns the following portion about the Networking state:

  • Dockerfile for on and off proxy
  • starting container using docker API
  • Connect to Docker API from Windows to external server
  • REST API for Docker Hub Registry
  • How do I access Windows eventlog of a Docker container
  • run nginx in docker with another application
  • "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"

    One thing to note is that I had to change the nameserver to (Google’s DNS) for necessary domain name resolution, due to the following error:

    Error resolving hostname; host=''
    Error initializing message pipeline;
    Error resolving hostname; host=''
    Error initializing message pipeline;

    You can find the source code of the Docker image I originally adopted at

    So my questions are:

    1. What does the ‘Networking’ state of a Bluemix container mean?
    2. Why does my container work locally but not on Bluemix?

  • Docker error: ln: target 'ps' is not a directory
  • Logs not generated in docker compose
  • Issues with importing large file in click-house
  • docker version fails on OS X
  • install additional python package on docker
  • Accessing Docker container other than ssh
  • 5 Solutions collect form web for “Bluemix Container status reads 'Networking'”

    Docker containers on Bluemix doesn’t support incoming UDP traffic routing yet. This feature is already planned for future updates as far as I know.
    This is the reason your container works fine locally, but remotely doesn’t receive traffic.

    ‘Networking’ state means that the networking is being created for your Container so that the public and private IPs for your Container can be accessed and routed to your instance. When a container gets stuck on Networking then it is typically a problem with the infrastructure rather than anything you have done.

    Please try to remove your container and recreate it to see if this should solve it. If not then you will need to open a support ticket to Bluemix (via the support link ‘Get Help’ on the Bluemix UI) to have the IBM Containers team investigate why your Container is having issues.

    1. Is the container able to get a response from the endpoint?

    You can just forward UDP traffic to Logentries, there is no need to switch to TCP.

    Maybe configure syslog-ng to connect directly to one of the IP’s associated to an ingestion node.

    Any of the blow should work.    105 IN  A    105 IN  A    105 IN  A    105 IN  A    105 IN  A
 105 IN A

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.