-
Notifications
You must be signed in to change notification settings - Fork 26
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
Deployment issues on M1 Mac #429
Comments
removing the image sounds excessive - maybe the last container is not cleaned up - what does |
Only containers unrelated to vespa when I run that command and I agree that removing the image is a ridiculous workaround seeing as images != containers, but yet it seems to work 🤷 |
I am working on reproducing the problem now |
Hi again, we have found that the signal handling in the start script does not seem to properly trap the TERM signal, so stopping the container isn't correct. We are working to find out more, and a fix, will update |
vespa-engine/docker-image#44 will fix the Docker stop issue and be released later this week - so can test pyvespa again then - I will update |
https://hub.docker.com/r/vespaengine/vespa/tags - 8.122.27 ( Can I ask you to test again with the latest image? if still an issue, I will find someone with an M1 and try to reproduce |
copy-pasting the "getting started" sample python scripts and running it twice with stop/rm between works fine for me.
|
Thanks Arne! |
I can also confirm this works. Thank you @kkraune + team (and sorry for not testing the fix sooner) |
The issue
I cannot deploy with
VespaDocker
multiple times without removing and re-pulling the image.After pulling
vespaengine/vespa
(usinglatest
), I can successfully deploy an instance using pyvespa on an M1 mac. If I stop and remove the container and then try to re-deploy, it timeouts on "waiting for application status". However, if I remove the image and then repull, the next deployment succeeds.System Info
vespaengine/vespa:latest
(I think8.116
-8.118
based on dates)0.22.0
The text was updated successfully, but these errors were encountered: