Dockermon - FAQ

From time to time, this may be updated. Or frequently, if questions are asked frequently enough.


Q: Something is broken, what do I do?

A: Typically that is what we hear as Software Developers. Please help us out and explain what it is that is broken, why you believe it’s broken and what it should do. That helps us to help you.


Q: Dockermon isn’t loading - What do I do?

A: First, did you change anything from the standard setup? If so, delete everything, start over and try again.

If you want to preserve your MySQL data leave the dockermon_db-data volume. Dockermon should be able to connect to that volume and you won’t lose any data

  1. Delete the Dockermon container from Docker
  2. Remove the dockermon_node_modules-fe and *_node_modules-be volumes
  3. Delete the webfreakeric/dockermon-monitor image.
  4. You can optionally do a docker image prune now, but it will remove any images you may have that aren’t being actively used.
  5. Remove the dockermon source code directory you originally downloaded.
  6. Go back to Step 1 of the README and start again. Do not modify any settings and attempt to rebuild.

If all goes well, you’ll be back up and running with your existing data. If for any reason you want to reset MySQL or are possibly having issues related to it, you can start the steps above again and delete the dockermon_db-data volume.


Q: My Container was created and Dockermon lost the data - what do I do?

A: This is a funny thing right? Docker re-creates the containers and their ID changes. Dockermon marks those containers as dead in the database and soft deletes them. They then get re-created under a new Id. That’s why currently the site acts strange when this shift happens.

A method to join these orphaned containers and preserve the stats is being investigated, but for now, they will remain orphans and ghosts in the database. Don’t worry, a cronjob will be written later to fix this.


Read More

Updated: