Full- stack container management as a service in production.
Everything you need to run a container based infrastructure in the cloud.
Cloud 66 offers a great way to build and manage Docker containers in production on bare metal, public cloud, or both. Using Cloud 66, developers can build containers directly from their code and deploy and manage it on their own server.
Their pitch: a complete solution for freelancers, agencies and enterprises anywhere around the world.
Deploy your Docker App with Cloud 66
Cloud 66 builds Docker stacks in two ways:
- Pulling your code from Git - This option uses Cloud 66 BuildGrid feature to build your Docker image directly from your git repository. You just need to provide a Dockerfile that specifies how you would like us to build the image. Once your image is ready, it is pushed to your servers, started, monitored and managed.
- User-provided image - You provide a Docker image that you have built by connecting your Cloud 66 account to any Docker repository, which we push to your servers, start and manage.
An End to End Stack
Cloud 66 offers a set of tools and practices to help you run a full end to end production Docker based stack. Cloud 66 Docker includes the following:
Container lifecycle management
Rolling out your Docker images to your servers, scaling, load balancing, port forwarding, lifecycle management, graceful draining and shutdown of workers, deployment rollbacks.
An internal Weave network that runs across all of your servers, allowing each server and container to have an internal IP address (on the 188.8.131.52 subnet). For example:
Server 1 (184.108.40.206) has Container 1 (220.127.116.11)
Server 2 (18.104.22.168) has Container 1 (22.214.171.124) and Container 2 (126.96.36.199)
Server 3 (188.8.131.52) has Container 1 (184.108.40.206) and Container 2 (220.127.116.11)
Containers can communicate with each other using the private address (on any port), regardless of the physical server the other container resides on. In other words, containers can communicate as if they were on the same server. The networking layer transparently maps between the two.
DNS / Service Discovery
An internal DNS service which assigns a DNS record to each of your Docker services and servers. For example, you can connect to your MySQL instance on mysql.cloud66.local, and this record will update automatically in case you switch your server. Services can be found at service_name.cloud66.local, and will use round-robin if you have more than one container for a service.
When building your Docker stack, you can either provide us with your own image, or let us create them for you with our powerful cluster of servers called BuildGrid. Your image is created based on your source code and a Dockerfile, which specifies how you want it to be created.
Using BuildGrid lets you focus on what you do best and avoids you having to create internal processes to output Docker images. You can even integrate your CI solution, so that new images are built and pushed to your servers once all your tests pass.
Any images created with BuildGrid are made available through Registry.
Docker-based stacks enjoy the same benefits as other Cloud 66 stacks, including:
- Deployed and managed databases (MySQL, PostgreSQL, MongoDB, Redis as well as non-database components like ElasticSearch and RabbitMQ)
- Database managed and verified backups and replication
- Nginx and load balancing
- Firewall management and brute force protection for web and SSH
- Team and organisations (ACL)
- Fast response 100% SLA DNS layer (Failover groups) for quick traffic switch overs
- Server vital sign metrics
- Intuitive UI
- API and command line