-
I've used kamal previously and had no issue but I'm getting a bit frustrated with my most recent project. Changes that I commit and deploy are not reflected on the server, it seems stuck on the first version I deployed. Any help would be appreciated 🙏 Basically my deploy failed because of a misconfiguration of
I could see that my latest change had not been applied, even though they were committed (locally and on remote). To work around it I ssh'd onto the server and ran
Then the next deploy the changes take hold:
I see the expected updates. However, any subsequent changes are again not picked up again and I have to do the whole clean out of docker on the target server (web) and run the deploy once more. Has anyone seen this before, or experienced anything like this? I have a feeling I'm missing something pretty fundamental. Other things I have tried:
Version & setup info
It's an Older rails app v6.1.7.8 using webpacker. The Dockerfile:
deploy.yml
deploy.staging.yml
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Worked out what was going on. New containers were going up but failing the healthcheck. The app was ok but took longer than the default time. Increasing that meant I got a successful deploy and the container was tagged appropriately. Using the |
Beta Was this translation helpful? Give feedback.
Worked out what was going on. New containers were going up but failing the healthcheck. The app was ok but took longer than the default time. Increasing that meant I got a successful deploy and the container was tagged appropriately.
Using the
kamal app exec -i bash -d staging
while in a fail state seemed to always default to the first container in the pile which was out of date (I've not looked into the logic of that).