[ 
https://issues.apache.org/jira/browse/KARAF-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Iurii updated KARAF-7549:
-------------------------
    Description: 
After migration from Karaf *4.2.0* to *4.3.6* I was able to run application via 
karaf.bat and via docker but have some issue with running application in 
kubernetes. I attached two log files:
 * standalone.txt - run via karaf.bat
 * docker.txt run via kubernetes

As you can see for some reason *FelixShutdown* process started destroying 
blueprint bundles (lines 310-312) in dockerlog file and kubernetes pod was 
marking as {*}CrashLoopBackOff{*}: 
{noformat}
org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
bundle org.apache.karaf.shell.core/4.3.6

org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
bundle org.apache.aries.blueprint.cm/1.3.2

org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
bundle org.apache.aries.blueprint.core/1.10.3

{noformat}
I used below command to run application in kubernetes:
{noformat}
kubectl run karaf --image=eu.gcr.io/container-registry-259614/geco:1.7.60 
--port=8181
{noformat}
I also attached dockerfile.

  was:
After migration from Karaf *4.2.0* to *4.3.6* I was able to run application via 
karaf.bat and via docker but have some issue with running application in 
kubernetes. I attached two log files:
 * standalone.txt - run via karaf.bat
 * docker.txt run via kubernetes

As you can see for some reason *FelixShutdown* process started destroying 
blueprint bundles (lines 310-312) in dockerlog file and kubernetes pod was 
marking as {*}CrashLoopBackOff{*}: 
{noformat}
org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
bundle org.apache.karaf.shell.core/4.3.6

org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
bundle org.apache.aries.blueprint.cm/1.3.2

org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
bundle org.apache.aries.blueprint.core/1.10.3

{noformat}
I used below command to run application in kubernetes:

kubectl run karaf --image=eu.gcr.io/container-registry-259614/geco:1.7.60 
--port=8181

I also attached dockerfile.


> CrashLoopBackOff in kubernetess pod
> -----------------------------------
>
>                 Key: KARAF-7549
>                 URL: https://issues.apache.org/jira/browse/KARAF-7549
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.3.6
>            Reporter: Iurii
>            Priority: Major
>         Attachments: DockerFileLogTrace.txt, Dockerfile, docker.log, 
> standalone.txt
>
>
> After migration from Karaf *4.2.0* to *4.3.6* I was able to run application 
> via karaf.bat and via docker but have some issue with running application in 
> kubernetes. I attached two log files:
>  * standalone.txt - run via karaf.bat
>  * docker.txt run via kubernetes
> As you can see for some reason *FelixShutdown* process started destroying 
> blueprint bundles (lines 310-312) in dockerlog file and kubernetes pod was 
> marking as {*}CrashLoopBackOff{*}: 
> {noformat}
> org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
> bundle org.apache.karaf.shell.core/4.3.6
> org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
> bundle org.apache.aries.blueprint.cm/1.3.2
> org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint 
> bundle org.apache.aries.blueprint.core/1.10.3
> {noformat}
> I used below command to run application in kubernetes:
> {noformat}
> kubectl run karaf --image=eu.gcr.io/container-registry-259614/geco:1.7.60 
> --port=8181
> {noformat}
> I also attached dockerfile.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to