Mount the Space Storage Volume¶
The container root directory specified by the
contains the mount points for all the containers
on the Docker system.
The container root (by default
/teamdrive) is the mount point for a
dedicated file system that provides the requirements outlined in chapter
By default, the directory
/teamdrive has already been created by the
td-webportal RPM package. However, if the Docker host is not the
same as the Web Portal machine, then you will have to create this
Note that due to restrictions of the Docker system, all data will be written to this directory as belonging to root.
Mount the file system and create the respective mount entry in
to enable automatic mounting of the file system at bootup. Please consult your
Operating System documentation for details on how to perform this step.
The Web Portal uses Docker containers to run the TeamDrive Agent. A container is started for each user that logs into the Web Portal.
The Docker containers can run on a machine or cluster that is separate from the Web Portal host which handles the login and manages the containers.
To install Docker enter the following:
[root@webportal ~]# yum install docker
The Docker daemon can be started and stopped using
service docker start
service docker stop.
By default, the Docker daemon is only accessable via a local socket. The Web Portal requires TCP connectivity. This is the case, even if Docker and the Web Portal are running on the same host.
To make Docker ccessable via TCP set the parameters
other_args in elarier versions of Docker) in the
/etc/sysconfig/docker file as follows:
After restarting Docker, the Docker API will be available on port 2375.
On the client side (the Web Portal host) you will now need to set the
DOCKER_HOST environment variable in order to use the
localhost below with the domain name of the Docker host:
[root@webportal ~]# export DOCKER_HOST=tcp://localhost:2375 [root@webportal ~]# docker images
The domain name (and port if not 2375) of the Docker host is stored in the
DockerHost system setting. This parameter is set during the
activation process described later (see Activating the Web Portal).
Installing the TeamDrive Agent Docker Image¶
Docker container images are available from the TeamDrive public Docker repostory on the docker hub. Here you will find a list of the taged images that have been uploaded by TeamDrive:
By default, the Web Portal uses a container image with the
Install this image on your Docker host using the following command:
[root@webportal ~]# docker pull teamdrive/agent:latest
Installing SSL certificates¶
The default Apache HTTP Server installation ships with self-signed SSL
certificates for testing purposes. We strongly recommend to purchase and
install proper SSL certificates and keys and to adjust the configuration in
/etc/httpd/conf.d/ssl.conf accordingly before moving the server into
The exact installation process depends on how you obtain or create the SSL key and certificate, please refer to the respective installation instructions provided by your certificate issuer.
Starting the Web Portal¶
After all configuration steps have been performed, we can start the TeamDrive Web Portal to conclude the initial installation/configuration.
To activate the
td-webportal background task you have to
start the service using the provided init script.
The configuration file
/etc/td-hosting.conf defines how this process is
run. You usually don’t have to modify these settings.
To start the
td-webportal program, use the
service command as user
[root@webportal ~]# service td-webportal start Starting TeamDrive Web Portal: [ OK ]
status option to the
service command to verify that the
service has started:
[root@webportal ~]# service td-webportal status yvvad (pid 2506) is running...
td-webportal does not start (process
yvvad is not running), check
the log file
/var/log/td-webportal.log for errors. See chapter
Troubleshooting for details.
Starting the Apache HTTP Server¶
Now the Apache HTTP Server can be started, which provides the TeamDrive Web
Portal functionality via
You can start the service manually using the following command:
[root@webportal ~]# service httpd start
At this point, the Web Portal’s web server is answering incoming requests from any web client that can connect to its address. For security purposes, you should not make it accessible from the public Internet until you have concluded the initial configuration, e.g. by blocking external accesses using a firewall.
Check the log file
for startup messages and possible errors:
[notice] mod_yvva 1.3.0 (May 5 2015 11:06:52) loaded [notice] Logging (=error) to: /var/log/mod_yvva.log [notice] Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations [notice] mod_pspace 1.6.17 Loaded; Build May 6 2015 12:42:39; Crash-Reporting-Disabled
Please consult chapter Troubleshooting if there is an error when starting the service.