No Logs (Again)

[hornkim]

Expected behavior

Kitmatic logs container output

Actual behavior

Get the Message "no Logs for this Container"

Information about the Issue

Kitematic 0.17.9
Docker Desktop 2.1.0.3
MacOS 10.14.6

Steps to reproduce the behavior

Just upgrade to latest docker, as prompted when you run Docker Desktop. Then it prompts you to upgrade Kitematic as the current is not compatible. Now Kitematic does not log !

This seems to be an ever repeating bug, #4712, #4610, that gets re-introduced all the time.The project needs to add as a test case to cover this.
I have had this issue a few times before, and down grading was a solution, will try but
Can anyone suggest what version to downgrade too, that does not invoke Docker to tell me they are not compatible.
Maybe need to go down a version of Docker Desktop , but who knows what one worked ?
I don't know what last version was I had, and trusted the prompt to upgrade !!!

[hornkim]

I down graded to 0.17.8 and still no logs.

[Trackhe]

I have taken the log fix. but I think he is not complete. Nevertheless, first built with it. if you notice again log error. please make new issue.

https://github.com/Trackhe/kitematic/releases

[jfabdo]

Just upgraded to the latest version of kitematic, also getting this issue on Mojave 10.14.5. I did not have this when I upgraded to 0.17.9 when docker was reporting that I was on a previous version of kitematic.

[hornkim]

Tried Trackhe's version 0.17.11 , see above, and Yes that fixed it. Cool !!! Kim

[jfabdo]

That worked for me as well. Thank you Trackhe!

[Trackhe]

Thanks and no problem. 👍

[fshafique]

Is anybody maintaining the issues list? Not trying to point fingers or lay blame. I just wanted to know if we have enough manpower on this project.
This issue hasn't been labelled as a bug yet, and I don't know if the developers/contributors even recognize this as an issue, even if we all give it a thumbs up.

[fshafique]

This is a duplicate of #5317 , except this thread has more traction.

[fshafique]

Also facing this issue with Windows 10 Pro (Build 17763).

[fshafique]

I have a temporary solution that doesn't require downgrading to a previous version. These are instructions for modifying v.0.17.9:

1. Shutdown Kitematic. Find where the Kitematic files were installed. Locate the \resources\app.asar file.

2. Install the asar tool: npm install -g asar

3. Extract app.asar into a folder. For example, to extract to "unpacked" folder: asar e app.asar unpacked

4. Edit the \utils\DockerUtil.js file where you unpacked it.
   Find this code:

   }, function (err, logStream) {
     if (err) {
       // socket hang up can be captured
       console.error(err);
       _ContainerServerActions2.default.error({ name: _this19.activeContainerName, err: err });
       return;
     }
   
     var logs = '';
     logStream.setEncoding('utf8');
     logStream.on('data', function (chunk) {
       return logs += chunk;
     });
     logStream.on('end', function () {
       _ContainerServerActions2.default.logs({ name: _this19.activeContainerName, logs: logs });
       _this19.attach();
     });
   });

   And replace with this:

   }, function (err, logBuffer) {
     if (err) {
       // socket hang up can be captured
       console.error(err);
       _ContainerServerActions2.default.error({ name: _this19.activeContainerName, err: err });
       return;
     }
   
     var logs = logBuffer.toString();
     _ContainerServerActions2.default.logs({ name: _this19.activeContainerName, logs: logs });
     _this19.attach();
   });

5. Repack everything into the "asar" file. For example: asar p unpacked app.asar
   Note: backup the old app.asar file, and remove to make space for the new one.

6. Restart Kitematic.

[juber-nunes]

Thanks a lot @Trackhe , works absolutely fine over here.