Deploying Docker through the Linode Marketplace
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Docker is a tool that enables you to create, deploy, and manage lightweight, stand-alone packages that contain that contain code, libraries, runtime, system settings, and dependencies that are required to run an application. These packages are called containers.
Each container is deployed with its own CPU, memory, block I/O, and network resources, without having to depend upon an individual kernel and operating system. While it may be easiest to compare Docker and virtual machines, they differ in the way they share or dedicate resources.
Deploying the Docker Marketplace App
The Linode Marketplace allows you to easily deploy software on a Linode using the Linode Cloud Manager.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Compute Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Fill out all required Options for the selected app as well as any desired Advanced Options (which are optional). See the Configuration Options section for details.
Complete the rest of the form as discussed within the Getting Started > Create a Linode.
Click the Create Linode button. Once the Linode has provisioned and has fully powered on, wait for the software installation to complete. If the Linode is powered off or restarted before this time, the software installation will likely fail. To determine if the installation has completed, open the Linode’s Lish console and wait for the system login prompt to appear.
Follow the instructions within the Getting Started After Deployment section.
Software installation should complete within 2-5 minutes after the Linode has finished provisioning.
Configuration Options
Docker Options
| Configuration | Description |
|---|---|
| Resource to Download | The url to a hosted Dockerfile or docker-compose.yml file to be used to assemble an image as part of the application creation process. |
| Command to run | A Docker Command to be run as part of the application creation process. |
| The limited sudo user to be created for the Linode | This is the limited user account to be created for the Linode. This account has sudo user privileges. |
| The password for the limited sudo user | Set a password for the limited sudo user. The password must meet the complexity strength validation requirements for a strong password. This password can be used to perform any action on the server, similar to root, so make it long, complex, and unique. |
| The SSH Public Key that is used to access the Linode | To access using SSH keys (recommended) rather than password, enter the public key here. For more information, see SSH add keys. |
| Disable root access over SSH? | Select Yes to block the root account from logging into the server via SSH. Select No to allow the root account to login via SSH. |
| Your Linode API Token. | Linode API access token is needed to create any DNS records. If you don’t have a token, you must create one to configure DNS. |
| Subdomain | The subdomain you want the installer to create a DNS record for during setup. The subdomain should only be provided if you also provide a domain and API Token. |
| Domain | The domain name you want to create as part of the application creation process. The installer creates a DNS record for this domain during setup if you provide this field along with your API Token. |
| Do you need an MX record for this domain? | Select Yes to create a basic
MX record for the domain. Select No to create no MX records. |
| Do you need an SPF record for this domain? | Select Yes to create a basic
SPF record for the domain. Select No to create no SPF records. |
General Options
For advice on filling out the remaining options on the Create a Linode form, see Getting Started > Create a Linode. That said, some options may be limited or recommended based on this Marketplace App:
- Supported distributions: Debian 9
- Recommended minimum plan: All plan types and sizes can be used.
Getting Started after Deployment
Docker is now installed and ready to use. The following steps provide a sample application to get you started with an easy example to demonstrate some basic Docker functionality. It is not necessary for Docker set-up.
Access Docker
After Docker has finished installing, you can access Docker from the console via SSH with the IPv4 address of the Linode:
Log out and log back in with the limited user account.
Install the unzip package from the package manager:
sudo apt install unzipDownload the example
node-bulletin-boardproject and unzip it:curl -LO https://github.com/dockersamples/node-bulletin-board/archive/master.zip unzip master.zipMove into the example project directory:
cd node-bulletin-board-master/bulletin-board-appBuild the image with the following command:
sudo docker image build -t bulletinboard:1.0 .Start a container with the image:
sudo docker container run --publish 8000:8080 --detach --name bb bulletinboard:1.0Visit the application in the browser by going to
http://198.51.100.0:8000, replacing the IP address with the public IP of the Linode.
To delete the container run:
sudo docker container rm --force bb
Next Steps
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
For more on Docker, checkout the following guides:
- An Introduction to Docker
- How to Use Docker Files
- How to Use Docker Compose
- How to Connect Docker Containers
- How to Create a Docker Swarm Manager and Nodes on a Linode
- Create and Deploy a Docker Container Image to a Kubernetes Cluster
- Manage a Docker Cluster with Kubernetes
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on