When one of my docker machine created virtual machines got changed by my cloud provider I was left in the dark. Out of a sudden docker-machine ssh no longer worked which comes at no surprise as the initially assigned IP address to me got changed.
In such a situation the SSH command line client has a way to specify the certificate to use when connecting to the VM:
ssh -i /home/john/.docker/machine/machines/T2fiware-postgres/id_rsa firstname.lastname@example.org
Replace `T2fiware-postgres` with the name of your docker created machine, ubuntu with the user the certificate was issued to and obviously the IP address with the one of your VM.
At times, Docker can be mind-boggling, especially when you strive for doing things “right”, which means following the “everything is a container” approach.
Now and then you will have to get large amounts of data into your container like restoring a database backup into a Docker-container. The Internets are full with good advice on how to do it (right), but given the combination of an out-of-docker database dump file and the intention to run a dockerized database with a data volume only container, the approach in this post was of help. I assembled the step-wise guide from the links in the footage, kudos goes to these authors.
Continue reading “Restore a Postgres Backup into a Docker container”
The previous post talked about the FIWARE project in general. This post will describe how to setup a virtual machine using Docker.
The FIWARE technical ecosystems (consisting eg. of the FIWARE Lab and Cloud) has little to offer on backend storage facilities. Thankfully, as being based on OpenStack, a developer should be fairly free to to set up anything up to the hearts content, as long as it fits into a virtual machine. Given that FIWARE supports Docker, I choose to go that route.
Continue reading “Docker on FIWARE”