If you want an all-in-one Docker for your Blog, you can use my new docker-ghostblog-cloudinary (the one used to run this blog).
This Docker is based on the docker-ghostblog image and it is adding a different images storage: Cloudinary. Any time you add an image, into a post, as post back image or into the blog settings area, all the images are sent directly to Cloudinary and then served through it.
Why you should store images somewhere else than your blog host?
For me it depends only on your host and the persons visiting it. The images, or in general the media files, are often the most busy and longest-running resources to download, so it is for me better to keep them as near as possible to the final "browser". And then we have to consider that, depending on your blog traffic, this can take lot of bandwidth and it can slow down the user experience.
Ok, ok, it is not the case for my blog :) BUT...
the blog server is in France and there are readers from everywhere. I think this decision will allow a faster loading for anyone.
If you want the Docker with a pre-configured Cloudinary plugin, you can take this one.
docker pull mmornati/docker-ghostblog-cloudinary:1.8.6 docker run -d -p 2368:2368 -e WEB_URL=http://test.blog -e SERVER_HOST=18.104.22.168 -e SERVER_PORT=4000 -e CLOUDINARY_URL=cloudinary://87237872387:aaaaaaaaaaaa@blog-mornati-net -v /opt/data:/ghost-override mmornati/docker-ghostblog-cloudinary:1.8.6
The CLOUDINARY_URL environment variable is used to configure the plugin with the information about your Cloudinary account.