Keycloak needs to restart to create the administrator user with external postgresql

Getting advice
,
1

hi guys im using keycloak from a custom docker Quay image that i already configured to use an external postgresql database, locally it works fine, but when im deploying it into a dev environment it needs to restart the server to create the administrator user to access the console, does anyone knows how to create the user previously so i dont need to restart the server?? or if there is any way to pre-configure the administrator user??

2

Set the environment variables KEYCLOAK_USER and KEYCLOAK_PASSWORD.
See also keycloak-containers/server at main · keycloak/keycloak-containers · GitHub

(Don‘t be confused of jboss/keycloak and the quay.io… images, quay.io is the origin, it‘s mirrored to docker hub.)

3

im already using this environment variables for the keycloak container

  DB_VENDOR
  DB_ADDR
  DB_DATABASE
  DB_USER
  DB_SCHEMA
  DB_PASSWORD
  KEYCLOAK_USER
  KEYCLOAK_PASSWORD
  KEYCLOAK_STATISTICS

and this environment variables for the postgresql container
POSTGRES_DB
POSTGRES_USER
POSTGRES_PASSWORD
and im using the standalone configuration to run keycloak locally and it works perfectly fine, but when i deploy it to AWS i use the following services
ECS
ECR
Alb
Ec2
RDS
route53
acm
network resources (public and private subnets, vpc, internet gateway, nat gateway, eips, route tables)
and it doesnt work, after thinking a while my guess is that i need to do some configuration for the alb to be able to run along keycloak, i also believe that i need to do some extra configuration to keycloak server to run on domain mode along alb

4

So you started this thread with asking for initial admin user and then throwing all and everything you deal with into the pot and guessing wildly different topics and making assumptions.

I won‘t help.
Good luck.

5

Thanks for your time !