This repository was archived by the owner on Jul 11, 2022. It is now read-only.
published docker hub image rhqproject/rhq-nodb does not work#6
Open
tarilabs wants to merge 1 commit intorhq-project:masterfrom
Open
published docker hub image rhqproject/rhq-nodb does not work#6tarilabs wants to merge 1 commit intorhq-project:masterfrom
tarilabs wants to merge 1 commit intorhq-project:masterfrom
Conversation
The published docker image rhqproject/rhq-nodb on the docker hub does not work and hangs forever once started.
I believe this is because the run script file invoke the installer `rhqctl install`, the installer does not find in the server properties a default admin password, hence prompts the user with:
```
The [rhq.autoinstall.server.admin.password] property is required but not set in [rhq-server.properties].
Do you want to set [rhq.autoinstall.server.admin.password] value now?
```
(I've checked by running this manually myself); but the installer is running as a java process inside the container itself, hence there is no way this is going to ever move on or start the application itself.
I've solved by proving a default `rhq.autoinstall.server.admin.password` property for the user `rhqadmin` as `rhqadmin`:
```
$ ./rhq-encode-value.sh
Property rhq.autoinstall.server.admin.password [y/n]: y
Password: rhqadmin
Encoded password for rhq-server.properties:
rhq.autoinstall.server.admin.password=x1XwrxKuPvYUILiOnOZTLg==
```
I believe that would be the solution, as additionally it would also follow similar style of already defined default passwords for other admins users (e.g.: `rhq.server.database.password`) in the server properties file. If there is a better solution kindly let me know.
Meanwhile, I will raise a PR accordingly to make explicit my proposed solution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As described in #5
The published docker image rhqproject/rhq-nodb on the docker hub does not work and hangs forever once started.
I believe this is because the run script file invoke the installer
rhqctl install, the installer does not find in the server properties a default admin password, hence prompts the user with:(I've checked by running this manually myself); but the installer is running as a java process inside the container itself, hence there is no way this is going to ever move on or start the application itself.
I've solved by proving a default
rhq.autoinstall.server.admin.passwordproperty for the userrhqadminasrhqadmin:I believe that would be the solution, as additionally it would also follow similar style of already defined default passwords for other admins users (e.g.:
rhq.server.database.password) in the server properties file. If there is a better solution kindly let me know.Meanwhile, I will raise a PR accordingly to make explicit my proposed solution.