-
-
Notifications
You must be signed in to change notification settings - Fork 936
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
Problem with quickstart and Docker #3302
Comments
quick solution : tested on colima macos and windows wsl2 |
Uh... now it seems to work! Thank you! |
configuration file and kratos version 0.13.0 incompatibility i guess |
Exactly same problem, the quick-start guide doesn't work on |
Sorry for the troubles, it's not acceptable when the quickstart is not working. We're taking a look at this. |
It might be good to indicate the |
Closing as 3267 has been fixed arm64 images are available (I use them on my M1) |
Preflight checklist
Describe the bug
Hello everyone, this is my first time trying Kratos and I ran into a problem that I couldn't solve on my own; I spoke with Vincent (@vinckr) on Slack who advised me to open this issue. In fact, I followed the quickstart instructions reported in the documentation (https://www.ory.sh/docs/kratos/quickstart):
Upon opening the welcome page:
http://127.0.0.1:4455/
All other pages are not accessible, for example:
http://127.0.0.1:4433/self-service/login/browser?aal=&refresh=&return_to=
http://127.0.0.1:4433/self-service/registration/browser?return_to=
http://127.0.0.1:4433/self-service/verification/browser?return_to=
In the terminal, I have a long list of errors similar to these:
I'm trying to execute the procedure with Docker Desktop on a Mac M1 with MacOS Ventura, the Kratos version is 0.13.0.
Reproducing the bug
cd Desktop
git clone https://github.com/ory/kratos.git
cd kratos
git checkout v0.13.0
docker-compose -f quickstart.yml -f quickstart-standalone.yml up --build --force-recreate
Relevant log output
Relevant configuration
No response
Version
0.13.0
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
Docker Compose
Additional Context
No response
The text was updated successfully, but these errors were encountered: