Assuming
- You are using Vagrant and Shell provisioner often (e.g when doing Windows provisioning you will end up using Powershell a lot)
- You have started running into the problem of reusing your scripts
Assuming
The exact list of plugins for enabling Docker commands within Jenkins jobs is somewhat unclear.
Looks like at least the Docker Build Step plugin is required to make this happen.
This does two things:
docker commands within Execute Shell stepsOne way to do this is to execute a simple Windows Powershell command using Ad-Hoc Ansible.
❗ note that shell does not work for Windows. The equivalent is win_shell.
| #!/bin/bash | |
| set -e | |
| ########### | |
| # AWS CLI Must be installed e.g using sudo apt install awscli. | |
| # This script cleans up your security group to remove old IP addresses from the rules for SSH, and | |
| # adds your current IP address. | |
| # This scenario is especially for cases where your ISP only allows dynamic IP addresses, or you | |
| # access AWS from multiple locations. |
Dangling images are "no name, no tag" images <none>:<none> created during image building. These images are bad because they consume disk space.
Reference.
docker images -f "dangling=true"