do you know if there is a switch where i can just ...
# ory-selfhosting
a
do you know if there is a switch where i can just create the tables and other things at the current version without migrations?
m
Hello @able-oxygen-89684 Please see my post here: https://ory-community.slack.com/archives/C02PSRUGUAV/p1740748593281769?thread_ts=1740718326.014399&cid=C02PSRUGUAV If you require professional support please get a contract with Ory! Open source software is provided "as is" without support. Ory is more active than ever.
a
Hahaha are you pitching me to be a customer even your getting started demo fails?
m
Hello @able-oxygen-89684 What getting started demo are you talking about? Can you link to it here please - I thought from your message you are already using Ory in production. We do have automated tests for the official quickstarts so they should work. If you are talking about helm charts those are "in incubation phase and use is at your own risk." If you want to use Ory software self-hosted in production with k8s then I would recommend to get a support contract yes.
a
Hi Vincent, at this point I don't want to use it all. Considering a simple hydra install with migration fails and the community support slack sends someone to sell support. I recommend you take it off of "open source" and shut down the community in this case since the meaning is clearly misunderstood or considered a farce. For God's sake, this problem has an issue that's a few years old and isn't fixed. Why would I spend money if I can't even see a hello world situation? Perhaps they shouldn't put you in front of the community
m
If you want to try out Ory Hydra please use the official quickstart: https://www.ory.sh/docs/hydra/self-hosted/quickstart I don't know what you were trying to do, but you just posted an issue related to upgrading Ory Hydra from v1.11.10 to v2.0.0. This is why I assume you are already running an old version of Hydra in production.
a
It's a blank cockroach databaseand a new installation running the migrate fails. It's funny that your quickstart doesn't have that. If you can run that quickstart with crib and get it to work without any modification to the code, I will sign today
m
I just tried it out, it works fine for me, applying migrations successfully etc. Please post here what steps you are taking exactly, if it still fails for you @able-oxygen-89684
a
Copy code
helm install hydra ory/hydra --namespace $NAMESPACE \
    --set "hydra.config.dsn=cockroach://${CRDB_USER}:${CRDB_USER}@${CRDB_HOST}/hydra?sslmode=${CRDB_SSL_MODE}" \
    --set "hydra.config.urls.self.issuer=<https://hydra.example.com/>" \
    --set "hydra.config.urls.login=<https://login.example.com/login>" \
    --set "hydra.config.urls.consent=<https://login.example.com/consent>" \
    --set "hydra.automigration.enabled=true" \
    --set "hydra.automigration.customArgs={migrate,sql, up,-e,--yes,--config,/etc/config/hydra.yaml}" \
    --set "maester.enabled=true"
however, i see that that sample is running an older version of crdb
the current version is
v25.1.0
also, how did you get it to work? 'docker compose -f quickstart.yaml -f quickstart-cockroach.yml up` fails
m
Yes I used this
Copy code
~/projects/hydra on #v2.3.0 > docker compose -f quickstart.yml \
  -f quickstart-cockroach.yml \
  up
You do need to checkout the latest release, it won't work on master
Copy code
git clone <https://github.com/ory/hydra.git>
cd hydra
git checkout v2.3.0
The helm charts from https://github.com/ory/k8s aren't tested and updated automatically - we do use them internally and for customers, but they might be out of date after a release for some time. So I would suggest to test Hydra out with the docker quickstart without k8s - it does depend what you want to evaluate I suppose, but I don't know what your use case is or what you are trying to achieve.
a
what docker images should i use? not the latesT?
looks like the
2.3.0
branch is using the
v2.2.0
image
same problem with the 2.2.0 image of hydra... ill try downgrading cockroachdb
m
Did you follow the quickstart here: https://www.ory.sh/docs/hydra/self-hosted/quickstart ? Or do you mean same problem when trying the helm charts? What are you trying to achieve? If you just want to evaluate Hydra then I would suggest to try without k8s - you probably dont need it to test out Hydra, unless I am misunderstanding something. Ory also offers (free) guided PoCs for commercial use cases if that helps. Btw on Ory Network you can just use the API on a free test account without running anything - the API is equivalent to self-hosting, so if you just want to test out something that might be the easiest way to do it.
a
I'm literally trying the quickstart with docker compose...
m
what error do you get? can you help me reproduce the problem? it works fine for me with a clean install.
a
Do you mind sending the logs from your migrate?
so the migrations pass on v24 of cockroach but not above that.
this means the migrations are not compatible with the new version of cockroach just released. I dont know if you care, but it will likely pop up for your "paying customers" soon . it seems like wrapping those two in a begin transaction/commit will fix it
m
Ah I see. I am not really familiar with that part, the team is probably aware. If it is an issue for you I can bring it up - you can ofc also create an issue in GitHub. As for logs I get a lot of these
Copy code
hydra-migrate-1 | time=2025-03-08T19:27:29Z level=info msg=Migration has not yet been applied, running migration. audience=application migration_file=migrations/20150101000001000000_networks.cockroach.up.sql migration_name=networks service_name=Ory Hydra service_version=v2.2.0 version=20150101000001000000
hydra-migrate-1 | time=2025-03-08T19:27:29Z level=info msg=> networks applied successfully audience=application migration_file=migrations/20150101000001000000_networks.cockroach.up.sql migration_name=networks service_name=Ory Hydra service_version=v2.2.0 version=20150101000001000000
hydra-migrate-1 | time=2025-03-08T19:27:29Z level=info msg=Migration has not yet been applied, running migration. audience=application migration_file=migrations/20190100000001000000_client.cockroach.up.sql migration_name=client service_name=Ory Hydra service_version=v2.2.0 version=20190100000001000000
hydra-migrate-1 | time=2025-03-08T19:27:29Z level=info msg=> client applied successfully audience=application migration_file=migrations/20190100000001000000_client.cockroach.up.sql migration_name=client service_name=Ory Hydra service_version=v2.2.0 version=20190100000001000000
hydra-migrate-1 | time=2025-03-08T19:27:29Z level=info msg=Migration has not yet been applied, running migration. audience=application migration_file=migrations/20190100000002000000_client.cockroach.up.sql migration_name=client service_name=Ory Hydra service_version=v2.2.0 version=20190100000002000000
hydra-migrate-1 | time=2025-03-08T19:27:29Z level=info msg=> client applied successfully audience=application migration_file=migrations/20190100000002000000_client.cockroach.up.sql migration_name=client service_name=Ory Hydra service_version=v2.2.0 version=20190100000002000000
....
hydra-migrate-1  | time=2025-03-08T19:27:45Z level=info msg=> jwk_index applied successfully audience=application migration_file=migrations/20240104181300000001_jwk_index.up.sql migration_name=jwk_index service_name=Ory Hydra service_version=v2.2.0 version=20240104181300000001
hydra-migrate-1  | time=2025-03-08T19:27:45Z level=info msg=Migration has not yet been applied, running migration. audience=application migration_file=migrations/20240129174410000001_client_add_logout_skip_consent_column.up.sql migration_name=client_add_logout_skip_consent_column service_name=Ory Hydra service_version=v2.2.0 version=20240129174410000001
hydra-migrate-1  | time=2025-03-08T19:27:45Z level=info msg=> client_add_logout_skip_consent_column applied successfully audience=application migration_file=migrations/20240129174410000001_client_add_logout_skip_consent_column.up.sql migration_name=client_add_logout_skip_consent_column service_name=Ory Hydra service_version=v2.2.0 version=20240129174410000001
hydra-migrate-1  | Successfully applied migrations!
Hello @able-oxygen-89684 following up here. Maybe we started off on the wrong foot - apologies if you had a rough start. In any case, maybe it would be good to take a step back and talk about what problem you are actually trying to solve - what do you want to achieve with Ory? I can make a recommendation based on your requirements. If you don't want to share this publicly feel free to contact me at vincent@ory.sh or book a meeting with me here.