It needs to build a docker container eventually given that’s the input they generalized for, but you can let fly build that container on their servers instead of locally. I don’t think there’s any requirement to run docker locally.
LostKobrakai
drobban
I tried to make the tooling work under freebsd. But perhaps it was pure skill issues at play on my part.
What you say sounds reasonable, and that was what I was hoping for… but… =)
Something failed anyhow, perhaps it was more tools in the chain that only works with Lindows. I dont really remember all the details on my endeavor to make it work.
But I did spend more then reasonable amount of time to try make it work =D
0
lessless
The remote builder works flawlessly on macOS; on other OSes, it may be enabled by passing --remote-only to the fly deploy.
Their support is amazing.
But
Their LHR region is the worst PaaS I ever used.
Starting from suspicious network latencies with GCP eu-west-2 region to advice from their support to redeploy until the VM is allocated on a server with enough free memory to accommodate RAM increase request 
, to service disruption when clients from EU were served times faster than from UK and LiveView was timing out for them, till suspicious RAM usage spikes and OOM crashes in the out-of-office hours on the internal tool.
They have the best DX out there, and flyctl is next to perfect, but using them is what actually makes me consider self-hosting.
Going back to the topic I want to mention, Ansible for DevOps [Leanpub PDF/iPad/Kindle] can help set up reusable and declarative deployment scripts.
2