PORTAINER

  • Linux
Please feel free to contact us
Go

About

Portainer stands as a versatile and user-friendly management solution tailored specifically for Docker environments. It serves as a lightweight yet powerful tool, offering an intuitive graphical interface that simplifies the complexities of container deployment, monitoring, and management tasks. With Portainer, users gain unprecedented visibility and control over their Docker resources, enabling them to effortlessly visualize and administer containers, networks, volumes, and images. Its centralized dashboard provides comprehensive insights and actionable data, empowering users to optimize resource allocation, troubleshoot issues, and streamline their Docker workflows with unparalleled ease and efficiency. Whether you’re a novice exploring Docker for the first time or a seasoned professional managing intricate containerized applications, Portainer’s seamless interface and robust feature set make it an indispensable companion for orchestrating Docker environments with confidence and clarity.

  1. Type virtual machines in the search.
  2. Under Services, select Virtual machines.
  3. In the Virtual machines page, select Add. The Create a virtual machine page opens.
  4. In the Basics tab, under Project details, make sure the correct subscription is selected and then choose to Create new resource group. Type myResourceGroup for the name.*.
  5. Under Instance details, type myVM for the Virtual machine name, choose East US for your Region, and choose Ubuntu 18.04 LTS for your Image. Leave the other defaults.
  6. Under Administrator account, select SSH public key, type your user name, then paste in your public key. Remove any leading or trailing white space in your public key.
  7. Under Inbound port rules > Public inbound ports, choose Allow selected ports and then select SSH (22) and HTTP (80) from the drop-down.
  8. Leave the remaining defaults and then select the Review + create button at the bottom of the page.
  9. On the Create a virtual machine page, you can see the details about the VM you are about to create. When you are ready, select Create.

It will take a few minutes for your VM to be deployed. When the deployment is finished, move on to the next section.

Connect to virtual machine

Create an SSH connection with the VM.

  1. Select the Connect button on the overview page for your VM.
  2. In the Connect to virtual machine page, keep the default options to connect by IP address over port 22. In Login using VM local account a connection command is shown. Select the button to copy the command. The following example shows what the SSH connection command looks like:

bashCopy

ssh azureuser@10.111.12.123

  1. Using the same bash shell you used to create your SSH key pair (you can reopen the Cloud Shell by selecting >_ again or going to https://shell.azure.com/bash), paste the SSH connection command into the shell to create an SSH session.

Usage/Deployment Instructions

Step 1:  Access the Portainer in Azure Marketplace and click on Get it now button.

A screenshot of a computer

Description automatically generated

Click on Continue and then click on Create.

A screenshot of a computer

Description automatically generated

 

 

Step 2: Now to create a virtual machine, enter or select appropriate values for zone, machine type, resource group and so on as per your choice.

 

 

Graphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generatedGraphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generatedGraphical user interface, text, application, email

Description automatically generated

Click on Review + create.

Step 3:  The below window confirms that VM was deployed.

Graphical user interface, text, application, email

Description automatically generated

 

Step 4:  Open port 9000 in security group by going to resource group –

  1. Select your network security group.
  2. Select Inbound security rules from the left menu, then select Add.
  3. You can limit the Source as needed or leave the default of Any.
  4. You can limit the Destination as needed or leave the default of Any.
  5. Choose a common Service from the drop-down menu, TCP. You can also select Custom if you want to provide a specific port to use like Port_4000.
  6. Optionally, change the Priority or Name. The priority affects the order in which rules are applied: the lower the numerical value, the earlier the rule is applied.
  7. Select Add to create the rule.
  8. Limit the Source port range as 9000. 

Graphical user interface, text, application, email

Description automatically generated

 

Step 5: Open putty and connect with your machine. Add IP address of the running virtual machine.

Step 6: Login with user name and password that you provided during machine creation.

How to access Portainer web interface

To access Portainer’s web interface, launch your web browser and browse this URL

http://server-ip:9000

 

NOTE: Sometimes, you can run into the error showing that the container has timed out for security purposes, as shown below.

 

portainer-container-timeout

 

As a workaround, restart the container using the docker stop and docker start commands as shown below.

 

docker stop contaner_ID

docker start contaner_ID

restart-portainer-docker-contaner

 

When you browse the URL, you will be required to create an administrative user. Therefore, provide a username and a strong password and click Create User.

 

create-admin-user-portainer-docker

 

Get started: Deploy a Docker container

 

Once you’ve created an admin user, you will be guided to the Quick Setup page. Since only one Portainer environment is currently sitting on your local environment, select the Get Started option.

 

portainer-quick-setup-get-started

 

Next, click the Live connect button. 

portainer-live-connect

 

You will be directed to your environment’s dashboard. On the left navigation bar, click Containers to start creating a container.

portainer-start-creating-docker-container

 

Next, click the add container button to the far left to create containers. You can already see that the Portainer image is listed as running on the container list.

 

portainer-container-list-add-container

 

On the Create Container page, specify the container details such as the container name, registry (by default, this is set to Docker Hub), and image. If you are unsure about the image name, click the Search button, which will take you to Docker Hub, where you can verify the correct image name.

 

create-container-portainer

 

Finally, click the Deploy the Container button.

 

portainer-deploy-container-after-specifying-details

 

A few moments later, the running container will appear on the container list, as shown below. In this example, we have deployed a Redis container.

 

docker-containers-portainer

 

You can confirm the running container on the command line by running docker ps once more. The output below shows an additional container running with the tag redis:latest. This confirms that our Redis container is running as expected.

 

verify-running-containers-docker-portainer

 

From the Portainer dashboard, you can perform a host of other operations, such as starting, stopping, restarting, and pausing containers.

 

Submit Your Request

Captcha

Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load. Amazon EC2 enables any developer to leverage Amazon’s own benefits of massive scale with no up-front investment or performance compromises. Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements.

The “Elastic” nature of the service allows developers to instantly scale to meet spikes in traffic or demand. When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.

 

Traditional hosting services generally provide a pre-configured resource for a fixed amount of time and at a predetermined cost. Amazon EC2 differs fundamentally in the flexibility, control and significant cost savings it offers developers, allowing them to treat Amazon EC2 as their own personal data center with the benefit of Amazon.com’s robust infrastructure.

When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.

Secondly, many hosting services don’t provide full control over the compute resources being provided. Using Amazon EC2, developers can choose not only to initiate or shut down instances at any time, they can completely customize the configuration of their instances to suit their needs – and change it at any time. Most hosting services cater more towards groups of users with similar system requirements, and so offer limited ability to change these.

Finally, with Amazon EC2 developers enjoy the benefit of paying only for their actual resource consumption – and at very low rates. Most hosting services require users to pay a fixed, up-front fee irrespective of their actual computing power used, and so users risk overbuying resources to compensate for the inability to quickly scale up resources within a short time frame.

 

You have complete control over the visibility of your systems. The Amazon EC2 security systems allow you to place your running instances into arbitrary groups of your choice. Using the web services interface, you can then specify which groups may communicate with which other groups, and also which IP subnets on the Internet may talk to which groups. This allows you to control access to your instances in our highly dynamic environment. Of course, you should also secure your instance as you would any other server.

 

Highlights

  • User-Friendly Interface.
  • Centralized Management.
  • Monitoring and Insights.
  • Security and Access Control.
  • Cross-Platform Compatibility.
  • Container Deployment.

Application Installed