Closed djeeg closed 6 years ago
Must have been host load, down to 30s today, which is acceptable (thought it might have been slow java random)
2018-03-05T15:12:03.773943614Z ===================================================================
2018-03-05T15:12:03.775800050Z Starting Supervisor. You can safely CTRL-C and the container will continue to run with or without the -d (daemon) option
root@c26fc248a948:/var/log/rundeck# tail /var/log/rundeck/rundeck.log
2018-03-05 15:12:32,995 [main] INFO grails.app.conf.BootStrap - Starting Rundeck 2.10.6-1 (2018-02-02) ...
2018-03-05 15:12:32,995 [main] INFO grails.app.conf.BootStrap - using rdeck.base config property: /var/lib/rundeck
2018-03-05 15:12:33,006 [main] INFO grails.app.conf.BootStrap - loaded configuration: /etc/rundeck/framework.properties
2018-03-05 15:12:33,072 [main] INFO grails.app.conf.BootStrap - RSS feeds disabled
2018-03-05 15:12:33,072 [main] INFO grails.app.conf.BootStrap - Preauthentication is disabled
2018-03-05 15:12:33,108 [main] INFO grails.app.conf.BootStrap - Rundeck is ACTIVE: executions can be run.
2018-03-05 15:12:33,114 [main] WARN grails.app.conf.BootStrap - The JVM default encoding is not UTF-8: US-ASCII, you may not see output as expected for multibyte locales. Specify -Dfile.encoding=UTF-8 in the JVM options.
2018-03-05 15:12:33,309 [main] INFO grails.app.conf.BootStrap - Rundeck startup finished in 381ms
Hi @djeeg
Thanks so much! I love Rundeck and hope my container is a good way to spread it's use 😄
You're correct, startup time does take a differing amount of time based on the available resources. I'll add a note to the README
Hi,
Im just starting out with rundeck, and your docker image seems to be the most widely used (1M+ pulls congrats!)
I was struggling a lot with even the most simple run, I couldnt see the admin screen to work
Until I accidentaly stopped configuration for a while, and magically the admin screen worked. Doing a bit more testing, it seems to take around 60s from the output of "Starting Supervisor. You can safely" for the website to become active.
Is that normal?
I gave the container uncontrained memory, but that didnt seem to make a difference.
Aside:
Trying to debug further, would i be right to assume i would need to turn on logLevel.debug in rundeck-config.properties Unfortuately, it doesnt look like i can control that setting with ENV variables.
Would another sed do the trick like this one?
https://github.com/jjethwa/rundeck/blob/master/content/opt/run#L152-L156
Let me know if you would like a PR