To connect to a database, you will need a client, and ideally one that you can quickly use through the command-line/terminal. Once you have your account, log in to it either in the UI or with docker login. That will be needed for some of the databases. Once you have Docker installed, make sure you have an account in the Docker Store - sign-up here. Easier to manage the containers in your system once you create them (start/stop/restart/delete). And while Kitematic is optional, I actually recommend you do so. Not only for this article but pretty much for everything you will eventually install in the future. If you haven't already done it, make sure you install Homebrew and Cask - package managers for Mac OS. Running RDBMS in containers may not be suited for production, but for development/testing environments? It is the perfect fit. If you really want to make your own developer life easier, get used to Docker and spin up databases in containers. In today's containerized world, this is past. Sometimes I'd face problems like dependency-hell, conflicts, native libraries missing, and would eventually end up running the databases in isolated VirtualBox VMs. Now, in the past when I used to run Linux on my laptops, I'd just install each database directly into my environment. If you like this article, please clap for it! Click on the little hands icon to the left or bottom of this page. If you are beginning your software development career and using Mac, and interested in using relational databases like MySQL/MariaDB, PostgreSQL, Microsoft SQL Server, Azure CosmosDB SQL or Oracle Database, then this article is for you! Setting up Database Servers for Development on Mac OS X Using Docker

Cinergy t2 mac os x