-
Notifications
You must be signed in to change notification settings - Fork 191
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
Hawkbit Server Docker container getting Exited immediately after start in WSL #1494
Comments
Hey @PrabhjeetSingh90 |
Hey @strailov This is the only logs we have from exited container | | | () | | | | | _ () | Eclipse hawkBit Update Server (v0.3.0M9) Go to https://www.eclipse.org/hawkbit for more information. 2023-11-09 10:09:28.476 INFO 1 --- [ main] org.eclipse.hawkbit.app.Start : Starting Start v0.3.0M9 using Java 17.0.7 on f431221626d8 with PID 1 (/opt/hawkbit/hawkbit-update-server.jar started by root in /opt/hawkbit) |
Hm, weird From the logs everything seems okay ... But there is no 'Started' log for the hawkbit update server, so if this is the last log I guess something outside hawkbit kills the process before it even started somehow ... |
The container is running a hawkbit server java application and I am assuming all the dependencies required to run the hawkbit server application is packaged with in the container image. Does It have any dependencies on the environment or the host Machines that is running the container? |
My first guess would be rabbitmq. You can check the dependency here - > hawkbit-runtime/docker/docker-compose-deps-mysql.yml In your case you use it with default profile so mysql won't be necessary (it uses h2 under the hood) But still if this is the problem why we do not see it from the hawkbit logs, and it won't happen from time to time it will happen consistently ... |
Hello,
we are observing Hawkbit Server Docker container getting Exited immediately after start in WSL. This is not reproducing Consistently but it is quite frequent. Here is the command that we are using to bring up the container in WSL linux Distibution(Ubuntu 20.04)
wsl docker run -d --name hawkbit-server -p 8080:8080 hawkbit/hawkbit-update-server:latest --hawkbit.server.ddi.security.authentication.gatewaytoken.enabled=true --hawkbit.server.ddi.security.authentication.gatewaytoken.key=%s
Is there any way we can debug this ?
Does anyone have seen this in your end?
Let us know if you need further info.
The text was updated successfully, but these errors were encountered: