-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Puppet downloads new Docker image when running in noop mode #241
Comments
I can't replicate your issue. With the following manifest initially I get docker images as you'd expect
If I update the manifest to the following then run with noop I get the following error
|
hi Dave, Thanks for taking a look. I think the key bit is:
Essentially the Try the following instead: First run a Puppet manifest that sets up an alpine image locally and ensures Docker and all the scripts are installed.
Now change the manifest to install a different package - eg
As you can see from the before/after, although we've only run the Ubuntu docker image manifest in |
Fault
When running Puppet with
--noop
it seems that this module will still pull Docker imagesExpectation
--noop
should be a no-impact mode and should not result in Docker images being pulled.Reproducing
To reproduce, have a manifest that defines a
docker::image
, eg:Then run puppet with
---noop
The text was updated successfully, but these errors were encountered: