Frequently Asked Questions

How is Blimp different than using Docker Compose on a machine booted by Docker Machine?

Docker Machine doesn’t support certain Docker Compose features. With Blimp:

  • Volumes just work without additional setup. With Docker Machine, bind volumes are mounted to the remote machine’s host, rather than the local machine.
  • You can access your containers over localhost. With Docker Machine, you have to manually setup tunnels to connect to the remote machine’s ports.

Blimp is also easier to set up and use since you don’t need an AWS account to get started. And is cheaper than running a dedicated cloud VM that sits unused when you’re not developing.

How is Blimp different from Docker Swarm or Kubernetes?

Docker Swarm and Kubernetes are container orchestrators used to run containers in production. Blimp is only meant to be used during development.

How do I access my services?

Just like with Docker Compose, you can access your services over localhost. Blimp inspects the ports declared in your docker-compose.yml, and creates an encrypted tunnel for each port.

Is this secure?

Yes. Your services run in an isolated sandbox in the Blimp Cloud. All communication between your local machine and the Blimp Cloud is encrypted.

Learn more in Security.

Can I share my services with my team members?

Blimp is actively working on a release that allows you to generate a unique URL to access your services.

This is useful to share in-progress work before you’re ready to deploy to your staging environment.

What configuration does it need?

Just a Docker Compose file. No modifications necessary.