Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCP Log in issues #55

Open
gtedone opened this issue Nov 26, 2023 · 0 comments
Open

SCP Log in issues #55

gtedone opened this issue Nov 26, 2023 · 0 comments

Comments

@gtedone
Copy link

gtedone commented Nov 26, 2023

I’m trying this image, with the target to containerize an existing on-premise and in-production installation.

So I started to play with the image in a non-production environment.

In a such condition, I was able to:

  • Use the latest image and even building the v1.18 image separately (using the Dockerfile found on v1.8 branch).
  • Use the above images with MySQL v8.0.35 (aligned to my current in-production DB engine).

Thrilled with this first good result, I then read the rest of README instructions on how to persist the secret.txt file, mount my db- and app-volumes (in the perspective to use them in production), finally I developed a docker-compose.yml (a little bit different from the original one, based on my needs, you can find it here).

But when I re-created the containers, suddenly I could't log in the SCP anymore with the default credentials.

I also tried to reset the ostadmin password as suggested here, but with no joy.

And this happens even if I go back to using the command-line methods proposed in the README.

It seems that I can recover the possibility to enter in the system only by an insane repetition of tear-down and re-creation of containers.

How can this be possible? Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant