I removed the CMD arguments and redeployed. I still have the same issue in the logs:
❌ Container image 692528610157.dkr.ecr.eu-west-3.amazonaws.com/z397f5a1f:5919104979414296799-55ae3a1300305e5243292843f9605e86f2d4385d failed to be build: Cannot build Application "z397f5a1f" due to an error with docker: ExitStatusError { exit_status: ExitStatus(unix_wait_status(256)) }
Issue seems to be building the image, did you try locally to build and run it?
If so would you mind sharing the command line you used?
ERROR: failed to solve: process "/bin/sh -c INTERACTIVE=false CI=true MB_EDITION=$MB_EDITION bin/build.sh" did not complete successfully: exit code: 255
No, I didn’t built it locally. If it helps, I built it directly in AWS using an EC2 instance 2 years ago or so. I remember I used the official Metabase Docker image on Dockerhub.
May be I don’t use the correct way to build Metabase with Qovery. Can you investigate and let me know what’s the right way of deploying this app ?
Just tried to deploy metabase from official image and it works perfectly.
May I ask why do you have to build it from your repo instead of using its official image?
I actually just followed the tutorial that suggests to start from a GitHub repo.
It indeed works great using Docker directly.
I have an additional question: deploying an app on several instances will create several links. Does Qovery integrate a load balancer to redirect seamlessly users ?
Several instances will be behind an nginx and it will be transparent for users.
I am not sure to understand this one, but if you meant application URLs, it won’t generate several URLs, everything will be behind one (or several if you add custom domains), but in anycase, you won’t be able to target one or the other instance, it will be transparent.
Yes, thanks a lot for your answers.
Last but not least: when I click on any of those 2 links (for example this one), Metabase is loading. It’s been like that since the deployment which is very strange.
I’ve found this github thread about kind of the same problem. They suggest installing haveged.
Just went to your app and it’s loading just fine here.
Regarding your entropy issue, I am just not sure we (Qovery) can do anything about it for you. I am not sure if changing your cluster instance type will fix this issue but you can try.
From my stand point, your app is running and deploying, from there, there is not so much I can do, I am not familiar with Metabase, and cannot give you more help than what they have in their documentation.
Container image 692528610157.dkr.ecr.eu-west-3.amazonaws.com/z397f5a1f:5919104979414296799-55ae3a1300305e5243292843f9605e86f2d4385d failed to be built: Cannot build Application “z397f5a1f” due to an error with docker: ExitStatusError { exit_status: ExitStatus(unix_wait_status(256)) }
Deployment failed
