docker-cronicle
docker-cronicle copied to clipboard
belsander
Docker container for a Cronicle single-server master node
When i shutdown the container, the pid-file from the log-volume isn‘t removed. If i start the container back, cronicle cant start because there is already a pid-file. If i disable...
fixed: use node:12-alpine to fix timer issue fixed: remove problematic ENV (websocket related) to fix dashboard loading issue fixed: install process for new version of cronicle fixed: drop privilege too...
install with command: ``` docker run --name cronicle --hostname localhost -p 3012:3012 intelliops/cronicle:latest ``` wait for a while, result:  logs: ``` [1605601124.224][2020-11-17 08:18:44][localhost][26][WebServer][debug][8][New incoming HTTP connection: c3][{"ip":"::ffff:172.17.0.1","num_conns":1}] [1605601124.225][2020-11-17 08:18:44][localhost][26][WebServer][debug][8][New...
This option cannot be set with the environment variable syntax being used here. For most scenarios the default should be fine. AFAIK using polling is not required in a Docker...
This is a UI issue observed with the `latest` tag, which runs version `0.8.28`. `0.8.28` is _also a tag_ which is slightly confusing :| See https://github.com/jhuckaby/Cronicle/issues/168 Tag `0.8.28` does not...
Solves #19. The image currently hangs on the initial screen, with a blank frame. After investigation, the removed env was causing the problem. Cronicle docs state: > Almost every configuration...
Running this `docker run --name cronicle --hostname localhost -p 3012:3012 intelliops/cronicle:latest` Boots up the image but the browser cannot login. We see the "Waiting for master server" for some time...
See: https://github.com/belsander/docker-cronicle/issues/24
There appears to be [support for loading](https://github.com/danwild/docker-cronicle#custom-configuration-file) a `config.json` file, however not for importing plaint text data that has been exported as [per the cronicle docs](https://github.com/jhuckaby/Cronicle#data-import-and-export). It would be very...
I have the non-docker version of this app and it runs fine, but I want to run this docker version and I ran into an issue. Most of my commands...
