Hi, thanks for providing this docker setup

I was working for me until I accidentally blew away my local image, built with your Dockerfile.

Attempting to rebuild the image again, with the file as is, reported the following error:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 winehq-stable : Depends: wine-stable (= 5.0.0~bionic)
E: Unable to correct problems, you have held broken packages.

changing the install from winehq-stable to wine-stable-i386 gave more details:

...

The following packages have unmet dependencies:
 wine-stable-i386:i386 : Depends: libfaudio0:i386 but it is not installable
E: Unable to correct problems, you have held broken packages.

Explicitly using a specific version winehq-stable=4.0.3~bionic has the same issue as above.

Explicitly using a specific i386 version wine-stable-i386=4.0.3~bionic, latest stable version prior to 5.0.0, or wine-stable-i386=4.0.2~bionic, the version in your docker hub latest image, causes the following exception:

-su: winecfg: command not found

All of which led me to find this blog post

https://www.linuxuprising.com/2019/09/how-to-install-wine-staging-development.html

Even though an update in the blog suggests the issue would be resolved by using the latest distribution eoan, it did not work for me.

So I finally got it to work by following the instructions to use the Wine OBS Repository:

	# add-apt-repository 'deb http://dl.winehq.org/wine-builds/ubuntu/ bionic main' && \
	wget -O- -q https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/Release.key | sudo apt-key add -  && \
	echo "deb http://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04 ./" | sudo tee /etc/apt/sources.list.d/wine-obs.list && \
	apt-get update && \
# Installation of wine, winetricks and its utilities and temporary xvfb to install latest winetricks and its tricks during docker build.
	apt-get install -y --no-install-recommends winehq-stable

Even though it is now working, I would rather use the source wine repository, do you have any suggestions on how to make it work the original repository in your docker file?

Thanks for the help

Hi
Having same issues as you do ...having it crash whenever... do you have a clue on what could be going on? I need to have it running 24/7 for live data on monitoring...can't afford having it crashing on me..
Any clue on where to look?
Thanks!

There is some kind of permissions problem when the container process writes to a log. This causes it to exit.

2019-06-15 17:38:28,333 INFO success: iqfeed-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
/bin/bash: /home/wine/DTN/IQFeed/wine.log: Permission denied
2019-06-15 17:38:28,340 INFO exited: wine-iqfeed-startup (exit status 1; not expected)
Traceback (most recent call last):
  File "/home/wine/pyiqfeed_admin_conn.py", line 52, in <module>
    format='%(asctime)s %(message)s')
  File "/usr/lib/python3.6/logging/__init__.py", line 1808, in basicConfig
    h = FileHandler(filename, mode)
  File "/usr/lib/python3.6/logging/__init__.py", line 1032, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python3.6/logging/__init__.py", line 1061, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/home/wine/DTN/IQFeed/pyiqfeed-admin-conn.log'
2019-06-15 17:38:28,483 INFO exited: pyiqfeed-admin-conn (exit status 1; not expected)

Looking at /home/wine/DTN/IQFeed/ the owner/group is root/root. I guess it should be wine/wine?

Hello,

It's a nice docker app that I recently start focus on it(quant related project).
I noticed a small error in the documentation of the docker-iqfeed repository. In the README.md file, under the Socket Connections section, the default port number for Level1Port is mentioned as 5009. However, in the Docker run command in the Usage section, the port mapping is given as -p 5009:5010. which is wrong
(https://www.iqfeed.net/dev/api/docs/Introduction.cfm)

I believe the correct port should be 5009, not 5010. This discrepancy might cause confusion for users trying to set up the IQFeed client.

just an small README error msg, but not critical, thanks again for providing this project

I see the following in the logs

{"log":"2021-10-28 18:15:03,765 INFO spawned: 'netcat' with pid 96\n","stream":"stdout","time":"2021-10-28T18:15:03.766396797Z"}
{"log":"2021-10-28 18:15:03,766 INFO success: Xvfb entered RUNNING state, process has stayed up for \u003e than 1 seconds (startsecs)\n","stream":"stdout","time":"2021-10-28T18:15:03.766801667Z"}
{"log":"2021-10-28 18:15:03,766 INFO success: pyiqfeed-admin-conn entered RUNNING state, process has stayed up for \u003e than 1 seconds (startsecs)\n","stream":"stdout","time":"2021-10-28T18:15:03.766904596Z"}
{"log":"2021-10-28 18:15:03,766 INFO success: wine-iqfeed-startup entered RUNNING state, process has stayed up for \u003e than 1 seconds (startsecs)\n","stream":"stdout","time":"2021-10-28T18:15:03.76702582Z"}
{"log":"2021-10-28 18:15:03,767 INFO reaped unknown pid 41\n","stream":"stdout","time":"2021-10-28T18:15:03.767152279Z"}
{"log":"2021-10-28 18:15:03,767 INFO reaped unknown pid 43\n","stream":"stdout","time":"2021-10-28T18:15:03.767250784Z"}
{"log":"2021-10-28 18:15:05,227 INFO success: netcat entered RUNNING state, process has stayed up for \u003e than 1 seconds (startsecs)\n","stream":"stdout","time":"2021-10-28T18:15:05.228001262Z"}
{"log":"2021-10-28 18:15:19,263 INFO pyiqfeed_admin_conn.\u003cmodule\u003e.144: iqfeed service not running.\n","stream":"stdout","time":"2021-10-28T18:15:19.263738693Z"}
{"log":"2021-10-28 18:15:35,311 INFO pyiqfeed_admin_conn.\u003cmodule\u003e.144: iqfeed service not running.\n","stream":"stdout","time":"2021-10-28T18:15:35.311605Z"}
{"log":"2021-10-28 18:15:51,364 INFO pyiqfeed_admin_conn.\u003cmodule\u003e.144: iqfeed service not running.\n","stream":"stdout","time":"2021-10-28T18:15:51.365029404Z"}
{"log":"2021-10-28 18:16:07,420 INFO pyiqfeed_admin_conn.\u003cmodule\u003e.144: iqfeed service not running.\n","stream":"stdout","time":"2021-10-28T18:16:07.420560783Z"}
{"log":"2021-10-28 18:16:23,472 INFO pyiqfeed_admin_conn.\u003cmodule\u003e.144: iqfeed service not running.\n","stream":"stdout","time":"2021-10-28T18:16:23.473049531Z"}

thanks for this repo,
I'm facing this error, Just wanted to know if anyone faced this or have an idea about it?
I've tried with older version and its the same.

I am able to get the pre-built jaikumarm/iqfeed:v62025-w6 docker image to run successfully, but a fresh build results in:

iqfeed      | 2022-03-27 04:47:06,273 INFO spawned: 'netcat' with pid 9
iqfeed      | 2022-03-27 04:47:06,275 INFO spawned: 'Xvfb' with pid 10
iqfeed      | 2022-03-27 04:47:06,277 INFO spawned: 'pyiqfeed-admin-conn' with pid 11
iqfeed      | 2022-03-27 04:47:06,278 INFO spawned: 'wine-iqfeed-startup' with pid 12
iqfeed      | 2022-03-27 04:47:06,279 INFO exited: netcat (exit status 1; not expected)
iqfeed      | Rotated `/root/DTN/IQFeed/wine.log' at Sun Mar 27 04:47:06 UTC 2022.
iqfeed      | 2022-03-27 04:47:06,475 INFO pyiqfeed_admin_conn.<module>.64:  PyIQFeed admin conn started.
iqfeed      | 2022-03-27 04:47:06,477 INFO pyiqfeed_admin_conn.<module>.144:  iqfeed service not running.
autoheal exited with code 7
iqfeed      | 2022-03-27 04:47:07,480 INFO spawned: 'netcat' with pid 89
iqfeed      | 2022-03-27 04:47:07,480 INFO success: Xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
iqfeed      | 2022-03-27 04:47:07,480 INFO success: pyiqfeed-admin-conn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
iqfeed      | 2022-03-27 04:47:07,480 INFO success: wine-iqfeed-startup entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
iqfeed      | 2022-03-27 04:47:07,480 INFO reaped unknown pid 31
iqfeed      | 2022-03-27 04:47:07,480 INFO reaped unknown pid 33
iqfeed      | 2022-03-27 04:47:07,485 INFO exited: netcat (exit status 1; not expected)
autoheal exited with code 7

It seems that there was an update to a dependency that broke the image?

I came across the README and noted the mention of the IQFeed client crashing intermittently. I'm curious:

1. Is this still an ongoing issue? I noticed there was a workaround using a health check script to monitor wine crashes in the wine.log file and subsequently marking the container as unhealthy. Has there been any update or fix for this since then?

2. Any elegant solutions? Is there a more elegant or seamless solution to handle this instead of relying on external services like docker stacks or docker-autoheal?

3. Alternate Recommendations? If the current repo is still facing this instability, do you recommend any other repositories or resources that might offer a more stable IQFeed client solution?

I appreciate your time and efforts in this project, and any guidance would be much appreciated.