0 votes
1 view

I was excited by the new version of Knowage 7.2, counting the days, hours, minutes ...

So, I provided the settings in the Dockerfile:

  • ARG KNOWAGE_VERSION = "7_2_0"
  • ARG KNOWAGE_REPO_VERSION = "7.2.0"
  • ARG KNOWAGE_EDITION = "CE"
  • ARG KNOWAGE_RELEASE_DATE = "20200730"

And I run the command to generate the image, brand new: "docker build -t knowage: 7.2.0."

Then, adjusted the docker-compose.yml, and I executed the command to create the containers "docker-compose up -d".
Both containers were successfully generated. Message Sucess!!
 

So, I accessed the link of the knowage that presented the login screen perfectly, and put the username and password (biadmin) and ...


The terrible message: Ooooooops! Invalid username or password, try again. crying 

What was missing?
Please I need help!!!

In console from browser, this print:

Failed to cabin-regular-webfont.woff:1 load resource: the server responded with a status of 404 ()
Failed to cabin-regular-webfont.ttf:1 Failed to load resource: the server responded with a status of 404 ()

Environment knowage_7.2.0, Linux, Docker, Container
asked Jul 31, 2020 in Docker by anderson.mattiola (1,120 points)
edited Jul 31, 2020 by anderson.mattiola | 1 view

1 Answer

0 votes

Hi

we are currently working on 7.2.0 docker container, it should be released soon.

Most likely authentication is not working in your docker container because 7.2.0 is brigning some changes in security, mainly the new password_encryption_secret configuration parameter: read this for details

https://knowage-suite.readthedocs.io/en/7.2/installation-guide/manual-installation.html#environment-variables-definition

Hope this helps

Regards

answered Aug 3, 2020 by dzerbett (1,860 points)

Dear dzerbett,
I made the changes according to the link you sent, and it worked perfectly.
I really appreciate your help.
Thank you very much. I am very happy rir

But anyway, as soon as the docker version of knowage 7.2 comes out, I'll download it to use. There may be several improvements that I was not able to implement in the dockerfile that I updated for my own use.

1,554 questions
1,017 answers
2,037 comments
2,568 users