Closed boych83 closed 8 months ago
I will just add link to the twitter with one answer: https://twitter.com/Sc00Fi/status/1595348091909070848 (if it worked)
Hi @kine, I'm the same person :) If you look, I linked this issue in a Twitter thread. @freddydk insisted that I report it here along with the rest of the information required by the template.
Did you find a solution to this issue? or is the issue still happening?
Looking in the output, it looks like there is a delay between the "Ready for connections!" and the following Initializing
2022-11-07T12:59:47.869151100Z Container Free Physical Memory is 6.4Gb
2022-11-07T12:59:47.869151100Z
2022-11-07T12:59:47.869785600Z Initialization took 23 seconds
2022-11-07T12:59:47.870360700Z Ready for connections!
2022-11-08T07:39:41.371069400Z Initializing...
2022-11-08T07:39:41.586898500Z Setting host.docker.internal to 192.168.1.4 in container hosts file (copy from host hosts file)
2022-11-08T07:39:41.661282900Z Setting gateway.docker.internal to 192.168.1.4 in container hosts file (copy from host hosts file)
2022-11-08T07:39:41.664760300Z Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
and also here:
2022-11-22T06:22:59.911733200Z
2022-11-22T06:22:59.921524200Z Initialization took 24 seconds
2022-11-22T06:22:59.921971500Z Ready for connections!
2022-11-22T06:36:08.583097600Z Initializing...
2022-11-22T06:36:08.936268700Z Setting host.docker.internal to 192.168.1.100 in container hosts file (copy from host hosts file)
2022-11-22T06:36:08.991570100Z Setting gateway.docker.internal to 192.168.1.100 in container hosts file (copy from host hosts file)
2022-11-22T06:36:09.000746700Z Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Do you know what happens here? Did this happen after he restarted his computer? or updated docker?
Hi @freddydk
At that time, we solved by manually changing the value. Since then everything has been working without a problem. At that time it was set up as a new laptop. Everything worked as expected for some days. One day in the morning (immediately after the fresh start ) this error showed up in the logs. It might be related to some win/docker upgrades, but I can't confirm.
BR, Bojan
Ok, will close this issue - and see if this ever re-appears. Thanks
Hi,
I have seen this now lately also several times... I can not really tell when this happens, but I know the cause fir this. the restartcounter.txt file and its content....in some strange cases it is empty or even includes some "strange" characters ... this leads to the can not convert to integer...we fix this most likely by just editing the file to include a 1 or 0 and containers are starting normal again. So, to mitigate this in the future a change to script could help to treat an non int value different ?!
I will try to add some resilience to this
perfect. And sorry for reopening! That was not my intention - I was just too stupid to check the status before hitting the send button :D
:-) - the reopen was me - I pressed the button manually:-)
The issue happened on all containers at the same day on PC which our new college using for local development. Script and output is for v21 container only. The initial run worked normally. Once our DB was restored, initialization was fine as well, and so were the following until the same initialization error occurred: Cannot convert value " " to type "System.Int32". Error: "Input string was not in a correct format." on all containers.
NavContainerHelper is version 4.0.6 Host is Microsoft Windows 10 Enterprise - 10.0.19044 Build 19044 Docker Client Version is 20.10.21 Docker Server Version is 20.10.21
Scripts used to create container and cause the issue
Full output of scripts
Full output of docker inspect