#Figuring out the deployment part, would
1 messages · Page 1 of 1 (latest)
Another alternative would be use the engine image as a base instead of using dind with the docker CLI. I recently deployed an API server plus the engine alongside, in a single container, to fly.io. This is how I built the app image itself: https://github.com/matipan/skunkworks/blob/main/roasty-server/.dagger/main.go#L40, and this is the fly.io part if you are interested: https://github.com/matipan/skunkworks/blob/main/roasty-server/.dagger/main.go#L71