Closed DavidMealha closed 1 year ago
Hey @DavidMealha, thanks for reaching out. Can you provide some additional details here please?
Publish docker image to a container registry
. Can you elaborate? Are we publishing the Appsmith image on an internal registry first before deploying? Any particular reason for this?Thank you for your patience with this.
Hello @sharat87, thank you for looking into it, I will try to answer your questions the best I can.
We are running on EKS but we have a standard pipeline for deployment which relies on the Dockerfile that lives inside the git repository, so we don't use the helm chart.
I have looked into it and there aren't any more logs, the pod fails after the last logs saying:
backend stdout | - Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.appsmith.server.repositories.ce.InviteUserRepositoryCE. If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository.
We are publishing to our container registry because it's the way the pipeline is setup, relates with 1.
@DavidMealha, hey, sorry, just seeing this.
Understood. That looks like a strange point for the container to stop working. Is it possible to share the Dockerfile and how the pipeline works, so I can try to reproduce the same thing on my end and troubleshoot please? Feel free to email the details to support-team@appsmith.com, if you'd prefer not to share them publicly here.
@DavidMealha were you able to get your issue resolved? I'm closing this for now but please do re-open it if you are still having trouble
Hey @sharat87 @Nikhil-Nandagopal, I must have missed the last messsage. I haven't isn't fixed no.
The Dockerfile is really simple, which might be the reason for it to stop?
FROM index.docker.io/appsmith/appsmith-ce:v1.8.5
So the CI/CD pipeline steps are these, beware that I don't have much knowledge around K8s and the rollout of pods:
Hey again @Nikhil-Nandagopal @sharat87, I have tried to troubleshoot a bit more the cause and it seems that it's failing with an out of memory error (exit 137). However the deployment memory usage doesn't reach near the limit, as you can see in the screenshot below.
@DavidMealha, sorry for the delay on this issue. Can you confirm if you have any other applications also running in your cluster, on the same node? Can you share the specs of this node, like it's CPU count, memory etc. please?
Closing since it's been dormant for months. Happy to reopen when we have more information. Thanks!
Is there an existing issue for this?
Description
I have successfully ran appsmith locally with docker-compose. However, now I'm trying to run it inside my company infrastructure (running EKS) which uses the Docker image to run any application.
I have tried it with versions
1.8.5
,1.7.14
and1.6.25
.According to the logs I can see some
stderr
logs in theeditor
but no error message.From my understanding there isn't any exception being raised, or atleast being logged but after these logs the pod restarts with a failure.
Steps To Reproduce
Public Sample App
No response
Version
Self-Hosted 1.8.5