{"id":258956,"date":"2026-07-13T16:36:33","date_gmt":"2026-07-13T13:36:33","guid":{"rendered":"https:\/\/1kitap1.com\/en\/docker-practical-guide-for-developers-and-devops-teams-bernd-oggl\/"},"modified":"2026-07-13T16:36:33","modified_gmt":"2026-07-13T13:36:33","slug":"docker-practical-guide-for-developers-and-devops-teams-bernd-oggl","status":"publish","type":"post","link":"https:\/\/1kitap1.com\/en\/docker-practical-guide-for-developers-and-devops-teams-bernd-oggl\/","title":{"rendered":"Docker Practical Guide For Developers And DevOps Teams – Bernd Oggl"},"content":{"rendered":"
\"<\/figure>\n

This service uses the current PostgreSQL image and uses the depends_on statement to indicate that the database server must also be started. As a command for the backup service, it\u2019s not the PostgreSQL database that should be started but pg_dump (here, in the multiline YAML Ain\u2019t Markup Language [YAML] notation). The backup file is stored in \/backup\/geonames.dump. In this case, it\u2019s a volume managed by Docker, but you can of course mount a local directory of your computer here.<\/p>\n

The pg_dump command reads from the environment variable PGPASSWORD, which is the data- base password defined in the environment section. The trick with this setup is that docker compose is called with both configuration files and the run statement for the backup service: docker compose -f docker-compose.yml \\ -f docker-compose.backup.yml run –rm backup This starts a container that runs the backup service and uses the pg_dump command to save the backup to \/backup.<\/p>\n

After that, the container gets deleted again (–rm), and the volume remains with the backup. 10.3 MongoDB With MongoDB, we want to introduce just one of the many NoSQL databases. Unlike relational database systems (RDBMS), NoSQL databases don\u2019t use tables and fixed structures. Data is stored in documents whose structures aren\u2019t bound to a strict schema. On one hand, this is very convenient because it saves complicated database schema adjustments, but on the other hand, it can also lead to confusion if each docu- ment has a different structure.<\/p>\n

Especially in the environment of modern web applications, NoSQL databases are very popular. The JavaScript Object Notation (JSON) format, which is widely used as an exchange format between the frontend and backend, can be stored or updated very conveniently in NoSQL databases, often without modifying it. MongoDB also has the reputation of scaling well with very large data volumes (keyword Big Data), even where relational databases reach their limits.<\/p>\n

\n

The Rheinwerk Computing series from Rheinwerk Publishing offers new and established professionals comprehensive guidance to enrich their skillsets and enhance their career prospects. Our publications are written by leading experts in the fields of programming, administration, security, analytics, and more. Each book is detailed and hands-on to help readers develop essential, practical skills that they can apply to their daily work.<\/p>\n

For further information, please visit our website: www.rheinwerk-computing.com. Philip Ackermann JavaScript: The Comprehensive Guide 2022, 982 pages, paperback and e-book www.rheinwerk-computing.com\/5554 Sebastian Springer Node.js: The Comprehensive Guide 2022, 834 pages, paperback and e-book www.rheinwerk-computing.com\/5556 Christian Ullenboom Java: The Comprehensive Guide 2022, 1126 pages, paperback and e-book www.rheinwerk-computing.com\/5557 Johannes Ernesti, Peter Kaiser Python 3: The Comprehensive Guide 2022, 1036 pages, paperback and e-book www.rheinwerk-computing.com\/5566 Bernd \u00d6ggl, Michael Kofler Git: Project Management for Developers and DevOps Teams 2023, 407 pages, paperback and e-book www.rheinwerk-computing.com\/5555 Rheinwerk Computing Bernd \u00d6ggl, Michael Kofler Docker Practical Guide for Developers and DevOps Teams Dear Reader, One line from Docker\u2019s mission statement has always stood out to me: \u201cWe handle the tedious setup, so you can focus on the code.\u201d<\/p>\n

I like to think that we do something simi- lar here at Rheinwerk. Having been internet-dwellers for a few decades now, most of us have had the experi- ence of picking up a new skill solely from web content. We\u2019ve cobbled together an edu- cation in, say, sourdough baking, via YouTube videos, blog posts, and how-to articles.<\/p>\n

However, online learning has its drawbacks: you\u2019ve got to sift out misinformation, you don\u2019t always know what you don\u2019t know, and content isn\u2019t always tailored to your needs (as anyone who has tried to bake at 8,000 feet above sea level using a standard recipe can testify)!<\/p>\n

So perhaps our version would be: \u201cWe curate the content, so you can focus on learn- ing.\u201d With all our books, our goal is always to present our reader with vetted informa- tion that\u2019s been thoughtfully organized and meets their needs. My first piece of advice to new authors is this: keep your reader in mind and write what they need to know. What did you think about Docker: Practical Guide for Developers and DevOps Teams? Your comments and suggestions are the most useful tools to help us make our books the best they can be.<\/p>\n<\/blockquote>\n

This is a short excerpt from the opening of “” by Unknown, quoted for review and introduction purposes. All rights belong to the copyright holders.<\/em><\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n