Jiale Zhi

I've also been experimenting with AWS to see what is the missing part. The good thins is that it seems the only thing missing from the current version of Fiber...

Can you try this branch `feature/cloud-providers`? I made a quick change to allow `fiber` command to take a docker registry as an input. You can run something like this: ```...

See #6

Can you provide a minimized test case (don't need to provide all of test_fiber_docker.py, just enough to reproduce this error)? Also, what OS are you running and what python version...

Hi @Basasuya , Fiber current doesn't work on Mac OS with Docker, see [doc](https://uber.github.io/fiber/platforms/). But yeah, the return value is a bug that needs to be fixed.

See https://github.com/uber/fiber/issues/27 Q2

Hi @danilopeixoto, docker swarm is currently not supported, but it could be added as a new backend. I'm less familiar with Docker swarm, not sure if it has similar APIs...

Just out of interest, what is your main use case? Trying to understand different use cases so that future priorities can be prepared.

pod/process-XXX uses the same image as the master process. For the master process, you specify the image when you launch it. Could you describe the issue a little bit more...

After you build and push image, do you still use `kubectl create job fiber-test --image=/fiber-testing -- python3 /root/run.py` ? Can verify that you launch fiber master process with the correct...