You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Morgan Kesler 21e7efac5a
misc formatting
1 year ago
data initial commit 1 year ago
images initial commit 1 year ago
.gitignore ignore changes to data dir 1 year ago misc formatting 1 year ago
docker-compose.yml update some things 1 year ago

SaltStack Dev Environment

This is my personal SaltStack dev environment setup using Docker containers to launch masters/minions. This is really oriented to my workflow and may not really fit with yours but here it is anyway.

Getting Started

Boot a master first:

docker-compose up -d salt-master

Then you can boot a minion

docker-compose up -d salt-minion

Verify it worked by doing:

docker-compose exec salt-master salt \*

Resetting everything just run:

docker-compose down -v

The -v flag will remove the pki volume which is important if you are doing a full reset.

Configuration, States and Other Data

Important directories


  • data/master/config is where you put the additional configuration for the master and maps to /etc/salt/master.d/
  • data/master/pillar you can store your pillar information here and maps to /srv/pillar
  • data/master/salt is where your state and other data can do and maps to /srv/salt

The master also has a docker volume called master_pki which maps to /etc/salt/pki and stores the PKI data


  • data/minion/config is the configuration for the minion and maps to /etc/salt/minion.d

Note: I don't store PKI data for minions so once the container is gone their key is lost.


  • data/db/init stick your .sql files here and it will be loaded on the first boot


This is based off of the project here but it's been heavily modified to fit my personal workflow.