Skip to content

docs(stack deploy): say how --resolve-image affects pulls #7198

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.

Sign up for GitHub

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

Open
locker95 wants to merge 1 commit into
base: master
Choose a base branch
from
+12 −0
Open

docs(stack deploy): say how --resolve-image affects pulls #7198

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/reference/commandline/stack_deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,18 @@ Creating service vossibility_ghollector
Creating service vossibility_lookupd
```

### Image pull (--resolve-image)

By default (`--resolve-image always`) the manager asks the registry for
a digest and workers pull that digest when they start a task. A moving
tag such as `:latest` therefore becomes whatever the registry has *now*,
not whatever happened to be cached on the node.

`--resolve-image changed` only re-resolves if the tag in the Compose
file changed. `--resolve-image never` leaves the image name as written
and does not query the registry on deploy (nodes still pull if they
do not already have the image).

You can verify that the services were correctly created:

```console
Expand Down