ChatGpt developed Module MMM-Dockerstat

Rags

@sdetweil Ok, is there any other method of achieving this?

mumblebaj

@Rags Welcome to the forum and great start.

Have you tried to run the module and found any issues?

Node_helper.js must be named node_helper.js
Your modules defines a bunch of dependent modules in node_helper.js but none of these were installed when you built the module so anybody who clones the module will not get of the dependent modules installed as they are not mentioned in package,js.
You declare ‘./Logger’ but it is never used. Do you need it?

If you fix the above issues the module starts. I do not run a Docker anywhere but the modules seems to working with the above issues fixed or at least it should get you going.

Always try and run the module first and check for issues and fix them if you can

Rags

@mumblebaj Thanks for the encouragement. I made the changes as suggested and updated the files on github. I also did some debugging and tried to resolve issues. However, I guess i am reaching a dead end. So any help will be appreciated greatly.

mumblebaj

@Rags Need to be bit more specific with what issues you are experiencing. If you are running you mirror with npm start then list the output from npm. Also check the developer console (shift + ctrl+i) and see if there are any errors there.

Rags

@mumblebaj
Thanks for the help, i am running with npm start. The display does not show the status of the docker containers. Instead the rotating arrow is continuously displayed.
I don’t know if the these error messages will indicate something, however here goes

The error msg with npm start;
02.04.2023 17:12.36.528] [LOG] Host 192.168.1.200 is offline.
[02.04.2023 17:12.36.530] [ERROR] (node:11566) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading ‘info’)
at /home/pi/MagicMirror/modules/MMM-Dockerstat/node_helper.js:59:21
at /home/pi/MagicMirror/modules/MMM-Dockerstat/node_modules/ping/lib/ping-sys.js:40:9
[02.04.2023 17:12.36.531] [ERROR] (node:11566) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
with developer console;

Failed to load resource: the server responded with a status of 404 (Not Found)
0.0.0.0/:1 Refused to execute script from ‘http://0.0.0.0:8088/modules/MMM-Dockerstat/fontawesome.js’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.
loader.js:194 Error on loading script: modules/MMM-Dockerstat/fontawesome.js
script.onerror @ loader.js:194

mumblebaj

@Rags Lots of issues in the code you had. I created a PR. Check it out.

Rags

@mumblebaj
Yes Sir. I noticed the changes committed by you and I immediately approved the merge commit. Please understand this is my first attempt and I had ChatGPT to help me. I guess we both are still learning. Well, I cloned the fresh updated repository and installed it. Now when i run it the constantly rotating arrow is not displayed anymore, but even the status of the containers are not being displayed. The npm start logs do not have any error messages. The dev console is also not indicating any issue. So probably some more debug is required. Sincere request to keep assisting till it is resolved.
Thanks

mumblebaj

@Rags Unfortunately I don’t have a docker running here so cannot test that portion of your code. You need to supply the docker name as an input parameter to feed into .exec(`sudo docker ps -f name=${payload.container} --format "{{.Names}} {{.Status}}"`)

Have you added this into the config.js?

sdetweil

@mumblebaj can u see the container names from inside a container?

mumblebaj

@sdetweil No idea. Never worked with containers before. (Shocking I know :astonished_face: ) Just gave him a bit of code to get the module running correct up until the point he has to check the status of the container code.