[keycloak-user] keycloak docker image from minikube

[Sebastian Laskawiec]

I've just checked it on my Fedora F30, Minikube v1.3.1, Docker
docker-1.13.1-67.git1185cfd.fc30.x86_64 and it worked fine.

You may try to find a reason why a pod was killed by invoking `kubectl
describe deployment/keycloak` and analysing events on the bottom of the
output.

Thanks,
Sebastian

On Sat, Sep 7, 2019 at 8:44 AM John Norris <johnnorris-10 at outlook.com>
wrote:

> Hi,
> I am trying to run keycloak from within minikube. This is minikube 1.31
> running on Windows. Minikube is running a VM via Virtual Box.
>
> Here is my yaml file
>
> apiVersion: apps/v1
> kind: Deployment
> metadata:
>   name: keycloak
>   labels:
>     app: keycloak
> spec:
>   replicas: 1
>   selector:
>     matchLabels:
>       app: keycloak
>   template:
>     metadata:
>       labels:
>         app: keycloak
>     spec:
>       containers:
>       - name: keycloak
>         image: jboss/keycloak
>         env:
>         - name: KEYCLOAK_USER
>           value: "admin"
>         - name: KEYCLOAK_PASSWORD
>           value: "123456"
>         ports:
>         - containerPort: 8080
>
> I have run other images and they work. But keycloak is killing minikube.
> So ...
>     > kubectl get pods
>     NAME                        READY   STATUS              RESTARTS   AGE
>     bikes-594d566c6d-65pdp      1/1     Running             0          14m
>     bikes-594d566c6d-klbhw      1/1     Running             0          14m
>     bikes-594d566c6d-qqppz      1/1     Running             0          14m
>     keycloak-66d55fcc58-5ssj9   0/1     ContainerCreating   0
> 5m50s
>
> Several minutes later
>
>     > kubectl get pods
>     Unable to connect to the server: http2: server sent GOAWAY and closed
> the connection; LastStreamID=69, ErrCode=NO_ERROR, debug=""
>
>     > minikube status
>     host: Running
>     kubelet: Running
>     apiserver: Error
>     kubectl: Correctly Configured: pointing to minikube-vm at
> 192.168.99.101
>
> If I run keubctl logs keycloak-66d55fcc58-5ssj9 then there are no errors
> though the last entry is
> [0m [0m17:43:03,402 INFO
> [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory]
> (ServerService Thread Pool -- 63) Node name: keycloak-66d55fcc58-5ssj9,
> Site name: null
> *** JBossAS process (128) received KILL signal ***
>
> So I am not sure if the problem is from keycloak or from minikube.
>
> can anyone help?
>
> Regards,
> John
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>