#Vapor Commands now hanging when run on Linux
1 messages · Page 1 of 1 (latest)
In both cases I'm using docker. The images for both mac and linux are created using the same Dockerfile but for different architectures. My mac is arm and my linux host is amd so I create the image on AWS EC2.
In both cases the startup is ./Run <command> --env production
Sorry I mean codewise
As in entrypoint.swift
What I'm trying to see is if you've migrated to the new template that correctly starts up the different pools needed for concurrency
Given you're binary is called Run I guess not?
Used by Vapor Toolbox’s new project command. Contribute to vapor/template development by creating an account on GitHub.
I did use the Vapor Toolbox as a basis for updating my Dockerfile but I missed the code change. Looks promising thanks. I'll do it and feedback.
I changed to using entrypoint.swift but it didn’t solve the problem. During further investigation I found that async commands work on my mac but only when invoked using docker compose. If I use docker run then they hang at the first async await just as they do on my linux host. Are there any docker options that might fix this? I’ll carry on looking.
Working fine now. I needed to update my commands to use the latest AsyncCommand protocol. Thanks @OxTim for the help I needed to get started on fixing this.