Remote.ItとDocker
私たち自身を含むすべての人にとってのメリット
Everyone loves Docker for a wide range of reasons. Internally, we run multiple copies of Remote.It agent on the same system. Each container is isolated so that each container can be a different version for testing. Docker doesn’t care if the host or containers are locally on a developer machine or hosted in AWS in an ECS or EKS cluster. Containers only use system resources on demand, so it’s very efficient. We don’t preallocate large systems or virtual machines. Containers can also automatically restart if anything goes wrong and it crashes. We often have to replicate complex test environments to mirror our customer’s deployment. Replication can be done using docker-compose or Kubernetes from the Docker desktop.
Our customers love the combined Remote.It and Docker solution as well. A huge benefit to many customers is by using Remote.It in a container environment, customers can take advantage of the service discovery functions within the container environment. For example, in a recent Kubernetes proof of concept for a customer, they had an EchoServer service and a Remote.It-Agent Service. When we configure the connection to the EchoServer Service, we just have to put ‘echoserver’ in the hostname for the connection. It doesn’t matter where in the cluster ‘echoserver’ is running. We can connect to it. If they add more pods to the Service, we don’t have to change anything.
Let’s take a step back for those new to Docker, containers, and Kubernetes.
Dockerとは？
Dockerは、開発者やDevOpsエンジニアがコンテナを構築、デプロイ、実行、更新、管理できるようにするプラットフォームです。
コンテナとは何ですか？
コンテナとは、アプリケーションのソースコードとオペレーティングシステムのライブラリや依存関係を組み合わせ、そのコードをあらゆる環境で実行できるように標準化された実行可能なコンポーネントです。
Developers can create containers without Docker. But Docker makes containerization faster, easier, and safer.
Dockerは、オープンソースのプロジェクトです。
Docker, Incは、商用版のDockerを販売している会社です。
How can you get started with Remote.It’s Docker image?
You can read about ourDocker solution or go directly to ourDocker Hub image with command line instructions.