Publish a web app as a Docker container by using the Azure Toolkit for Eclipse
Docker containers are a widely used method for deploying web applications. By using Docker containers, developers can consolidate all their project files and dependencies into a single package for deployment to a server. The Azure Toolkit for Eclipse simplifies this process for Java developers by adding Publish as Docker Container features for deployment to Microsoft Azure. This article walks you through the steps required to publish your applications to Azure as Docker containers.
More information about Docker is available on the Docker website.
The Azure Toolkit for Eclipse requires the following software components:
Eclipse IDE for Java EE Developers, Mars, or later. You can download it from the Eclipse website.
A Java Developer Kit (JDK), version 1.8 or later.
An operating system. The Azure Toolkit for Eclipse has been tested on the following operating systems:
For more information, see the Azure Toolkit for Eclipse page at the Eclipse Marketplace.
Publish your web app to Azure by using a Docker container
Open your web app project in Eclipse.
To start the Publish as Docker Container wizard, do either of the following:
In the Navigator view, right-click your project, click Azure, and then click Publish as Docker Container.
On the Eclipse toolbar, click the Publish button, and then click Publish as Docker Container.
The Deploy Docker Container on Azure wizard opens.
In the Type an image name, select the artifact's path and check a Docker host to be used window, do the following:
a. In the Docker image name box, enter a unique name for your Docker host. (The wizard automatically creates a name, but you can modify it.)
b. The Hosts area displays any Docker hosts that you have already created. Do either of the following:
- If you have an existing Docker host, you can deploy your web app to it.
To create a new Docker host, click Add.
The Create Docker Host dialog box opens.
In the Configure the new virtual machine window, specify the following options for your Docker host. (The wizard automatically generates most of the options for you, but you can modify any of them.)
a. Name: Enter a unique name for the Docker host. (It is not the same as the Docker image name that you specified earlier.)
b. Subscription: Enter the Azure subscription that you use for your host.
c. Region: Enter the geographical region where your host is located.
d. On the Host OS and Size tab:
- Host OS: Enter the operating system for the virtual machine that contains your host.
- Size: Enter the virtual-machine size for your host.
e. On the Resource Group tab:
- New resource group: Create a new resource group for your host.
- Existing resource group: Enter an existing resource group from your Azure account.
f. On the Network tab:
- New virtual network: Create a new virtual network for your host.
- Existing virtual network: Enter an existing virtual network from your Azure account.
g. On the Storage tab:
- New storage account: Create a new storage account for your host.
- Existing storage account: Enter an existing storage account from your Azure account.
In the Configure log in credentials and port settings window, select one of the following options:
- Import credentials from Azure Key Vault: Specifies a previously saved set of credentials that are stored in your Azure subscription.
An Azure Key Vault that's created with a specific account or service principal is not automatically accessible by another account or service principal that shares the subscription. To allow another account or service principal to use the Key Vault, you must use the Azure portal to add the account or service principal.
New log in credentials: Creates a new set of login credentials. If you select this option, do the following:
On the VM Credentials tab, choose one of the following options for the virtual-machine login credentials of your Docker host:
- Username: Enter the username for your virtual machine login credentials.
- Password and Confirm: Enter the password for your virtual machine login credentials.
SSH: Enter the Secure Shell (SSH) settings for your Docker host. You can choose from the following options:
- None: Specifies that your virtual machine will not allow SSH connections.
- Auto-generate: Automatically creates the requisite settings for connecting via SSH.
- Import from directory: Specifies a directory that contains a set of previously saved SSH settings. The directory must contain the following two files:
- id_rsa: Contains the RSA identification for a user.
- id_rsa.pub: Contains the RSA public key that is used for authentication.
On the Docker Daemon Credentials tab, specify the following options:
- Docker Daemon port: Enter the unique TCP port for your Docker host.
TLS Security: Enter the Transport Layer Security settings for your Docker host. You can choose from the following options:
- None: Specifies that your virtual machine will not allow TLS connections.
- Auto-generate: Automatically creates the requisite settings for connecting via TLS.
- Import from directory: Specifies a directory that contains a set of previously saved TLS settings. More specifically, the directory must contain the following six files:
- ca.pem and ca-key.pem: Contain the certificate and public key for the TLS Certificate Authority.
- cert.pem and key.pem: Contain the client certificate and public key that is used for TLS authentication.
- server.pem and server-key.pem: Contain the server certificate and public key for the host.
After you have entered all of the preceding information, click Finish.
In the Deploy Docker Container on Azure wizard, click Next.
In the Configure the Docker container to be created window, do the following:
a. In the Docker container name box, enter a unique name for your Docker container.
b. Choose one of the following Docker images:
Predefined Docker image: Specifies a pre-existing Docker image from Azure.
The list of Docker images in this box consists of several images that the Azure Toolkit has been configured to patch so that your artifact is deployed automatically.
Custom Dockerfile: Specifies a previously saved Dockerfile from your local computer.
This is a more advanced feature for developers who want to deploy their own Dockerfile. However, it is up to developers who use this option to ensure that their Dockerfile is built correctly. The Azure Toolkit does not validate the content in a custom Dockerfile, so the deployment might fail if the Dockerfile has issues. In addition, the Azure Toolkit expects the custom Dockerfile to contain a web app artifact, and it will attempt to open an HTTP connection. If developers publish a different type of artifact, they may receive innocuous errors after deployment.
c. Port settings: Enter the unique TCP port binding for your Docker container.
After you have completed all of the preceding steps, click Finish.
The Azure Toolkit begins deploying your web app to Azure in a Docker container.
For additional resources for Docker, see the official Docker website.
For more information about the Azure toolkits for Java IDEs, see the following links:
- Azure Toolkit for Eclipse
- Azure Toolkit for IntelliJ