Closed ghost closed 4 years ago
New release seems broken, pulling an older, known-good release fixed it for me:
docker stop py3-kms
docker rm py3-kms
docker pull ekonprof18/pykms@sha256:1deca36a2f3ecabc1902f90475fcf9490135f03a03f0fb8e2dd0a9ca03b4f5f0
docker run -d --name py3-kms \
-p 8080:8080 \
-p 1688:1688 \
-e IP=0.0.0.0 \
-e PORT=1688 \
-e SQLITE=true \
-e HWID=RANDOM \
-e LOGLEVEL=INFO\
-e LOGFILE=/var/log/py3-kms.log \
-v /etc/localtime:/etc/localtime:ro \
-v /var/log:/var/log:rw \
--restart unless-stopped ekonprof18/pykms:py3-kms
New release seems broken, pulling an older, known-good release fixed it for me:
docker stop py3-kms docker rm py3-kms docker pull ekonprof18/pykms@sha256:1deca36a2f3ecabc1902f90475fcf9490135f03a03f0fb8e2dd0a9ca03b4f5f0 docker run -d --name py3-kms \ -p 8080:8080 \ -p 1688:1688 \ -e IP=0.0.0.0 \ -e PORT=1688 \ -e SQLITE=true \ -e HWID=RANDOM \ -e LOGLEVEL=INFO\ -e LOGFILE=/var/log/py3-kms.log \ -v /etc/localtime:/etc/localtime:ro \ -v /var/log:/var/log:rw \ --restart unless-stopped ekonprof18/pykms:py3-kms
I maked new release on ekonprof18/pykms:py3-kms 15 days a go, and it's work great with python version 3.6. Now, i want make it work with python version 2.X.
I believe there might be an issue with this release that is affecting some users (like us) but not all, as you aren't having any problems.
When I reverted the release as I described above, it started working again.
This was a clean Debian 10 install, with the latest version of docker and then this image (with the arguments above). A single Server 2012 R2 was attempting to connect.
@6ec123321
In pykms_Sql.py an import sys
should be enough.
Can you try if it's so ?
Fixed with c1fa144
How can I fix this?