Bobcares

Container Volumes In Portainer | How To Add It?

by | Jan 28, 2023

We can practically do anything we need to do to work with the Docker containers thanks to the Docker container volumes in Portainer. With our 24/7 Docker Hosting Support Services, we offer solutions to your Docker queries.

Why do we need Docker container volumes in Portainer?

It may be not easy to get data from another container if we install the container without a volume while deploying an application or service that saves data. This is because the data will be stored inside the container. Even worse, if something happened to that container, the data it contained might be lost.

container volumes in portainer

Volumes can help with that by providing permanent storage for the containers. In this manner, we are able to build a container that uses an external volume. The data is still there in the volume even if something were to happen to the container. With the help of Docker container volumes in Portainer, we can essentially do anything to work with the Docker containers.

The steps involving the addition of container volumes in Portainer are as follows:

1. Setting-up Persistent Volume

2. Setting-up Volume In Portainer

Setting-up Persistent Volume

The steps to set up the volume on the server are as follows (Here, we’re using Samba share, an open-source Microsoft Windows file-sharing system, as the persistent volume):

1. Install the required dependencies by first logging into the Linux server:

sudo apt-get install samba cifs-utils -y

2. Next, use the command: to create a directory to store the Samba share.

mkdir ~/data

3. Now make a password for the Linux user with the below code:

sudo smbpasswd -a USER

4. Type and verify the new password when asked.

5. Now activate the Samba user using the command:

sudo smbpasswd -e USER

6. Edit the Samba configuration file to add a new share using the following command:

sudo nano /etc/samba/smb.conf

7. Include the below line at the end of that file:

[data]path = /home/jack/databrowsable = yeswritable = yesread only = no

8. Save and close the file.

9. Restart Samba with:

sudo systemctl restart smbd

Setting-up Volume In Portainer

1. Firstly, log into the Portainer instance.

2. Select Volumes from the left sidebar.

3. Provide a name for the new volume in the resulting window.

4. Next, move the Use CIFS volume ON/OFF slider until it is in the ON position.

5. In the CIFS Settings section, enter the IP address of the Linux server, and the share name.

6. Choose CIFS 3.0 from the version CIFS version drop-down.

7. Provide the username we added to Samba, and then type the password.

8. Finally, click on the “Create the volume” option.

[Looking for a solution to another query? We are just a click away.]

Conclusion

In this article, we’ve provided the detailed steps from our Support team to include a Docker container in Portainer.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF