Public Repository

Last pushed: 3 years ago
Short Description
Dockerized IQFeed ( client
Full Description


docker run -e LOGIN=<your iqfeed login> -e PASSWORD=<your iqfeed password> -p 5009:5010 -p 9100:9101 bratchenko/iqfeed

You should see out put like this:

Connecting to port 9300 Disconnected. Reconnecting in 1 second. Connecting to port 9300 Disconnected. Reconnecting in 1 second. fixme:thread:GetThreadPreferredUILanguages 52, 0x32fac4, 0x32fb34 0x32facc fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:thread:GetThreadPreferredUILanguages 52, 0x32f880, 0x32f8f0 0x32f888

That's totally ok.

Wait until you start seeing log lines that have word "Connected" in them. They should look like this:

S,STATS,,60002,500,0,1,0,5,0,Aug 20 2:42PM,Aug 20 2:42PM,Connected,,416828,0.55,0.02,0.03,3.94,0.11,0.18,

Here you go, now you should be able to connect to ports 5009 or 9100 to the current machine as if you're connecting to an IQFeed client.

If you don't start seeing "Connected" lines in about 1 minute, then you probably entered login or password incorrectly. Unfortunately, IQFeed doesn't say anything about it, just doesn't connect.


This image runs an IQFeed client (version using Ubuntu 14.04 and wine.

It exposes IQFeed ports 5009 and 9100 as 5010 and 9101 correspondingly. Port change is because IQFeed listens on localhost and proxy embeded into container translates those ports to 5010 and 9101.

Image accepts following environment variables:

  • LOGIN - IQFeed account login (not the one for site, by for IQFeed client)
  • PASSWORD - IQFeed account password
  • APP_NAME - application name that is passed to the IQFeed server (if you don't have one, or don't know it, it will still work with IQFEED_DEMO app name)
  • APP_VERSION - application version that is passed to IQFeed (defaults to

Building your own version

See intstructions here:

Docker Pull Command