Note that if you plan to access rucio outside of localhost you need to update the extra_hosts and ports within the rucio service in the ./etc/docker/dev/docker-compose.yml file:
docker-compose --file ./etc/docker/dev/docker-compose.yml up -d
dockerexec -it dev_rucio_1 /bin/bash
The rest of the commands are to be executed within the Docker container
Initialize the database
Terminal
|
tools/run_tests_docker.sh -i
Update the ca-certificates package
The image has python3 linked in /usr/bin/python but yum requires python2.
One workaround is to change the first line of /usr/bin/yum and /usr/libexec/urlgrabber-ext-down to use /usr/bin/python2:
vi /usr/bin/yum
change "python" to "python2" in the first line
vi /usr/libexec/urlgrabber-ext-down
now change "python" to "python2" in the first line
Terminal
|
yum update ca-certificates
(Optional) Generate New Cert for Custom IP
If you will be accessing the Rucio server outside localhost, you will need to update the cert to include your IP or domain. Replace PUBLIC_IP_HERE with your IP or add a DNS entry for a custom domain name.
If you updated certificates to include a custom domain, you may need to restart the server. You can do this by restarting the containers associated with the rucio server:
A WebUI instance with the minimal configuration can be started like this:
Note that the paths below beginning with /root/rucio reference the path to the rucio project that was git cloned in Rucio Step-by-step above. The /rucio folder will likely be somewhere else on your machine, so make sure to update those references before executing the docker run command.
Now you should be able to access the Rucio WebUI at https://localhost:443 or https://<your-public-ip> (the app is listening on port 443, so as long as you use https, you shouldn't need the port number) and login with the demo credentials:
Username: ddmlab
Password: secret
Step 3 - Rucio Client
If you are launching the container from the same host that Rucio server is running on: