Skip to content
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

Docker-stack container image:tag not updating when it is changed #8075

Open
valentinedwv opened this issue Nov 18, 2022 · 3 comments
Open

Docker-stack container image:tag not updating when it is changed #8075

valentinedwv opened this issue Nov 18, 2022 · 3 comments

Comments

@valentinedwv
Copy link

Bug description

  • Created a stack from a docker-compose hosted in github.
  • I changed created a branch, in github
  • I changed the label in the docker-compose file
  vue-services:
    image: nsfearthcube/ec_facets_api_nodejs:latest

to

  vue-services:
    image: nsfearthcube/ec_facets_api_nodejs:prod_coll_collab

When I redeploy the stack, the services details: image keeps on reverting to image: nsfearthcube/ec_facets_api_nodejs:latest

Expected behavior
The services>container image should reflect the image:label from the docker-compose file.

Portainer Logs
Provide the logs of your Portainer container or Service.
You can see how here
protainerlogs.txt

Steps to reproduce the issue:

  1. Go to 'stacks'
  2. Click on 'create stack from git
  3. Scroll down to 'deploy.'
  4. open project in github update the docker-compose in git to point at a new image:tag
  5. go portainer, open stacks
  6. pull and redeploy.
  7. go to services, see that contianer, that image points at original image:tag
  8. in service, change container image to image:tag, service restarts
  9. go to stacks > pull and redeploy stack
  10. go to services, see that contianer, that image points at original image:tag

Technical details:

  • Portainer version: 2.16/2.15
  • Docker version (managed by Portainer):Swarm 20.10.21
  • Kubernetes version (managed by Portainer):
  • Platform (windows/linux):ubuntu 20
  • Command used to start Portainer (docker compose -p base --env-file $envfile -f base-machine-compose.yaml up -d):
  • Browser:
  • Use Case (delete as appropriate): Using Portainer in an academic setup.
  • Have you reviewed our technical documentation and knowledge base? Yes

Additional context
stacks are here.

@tamarahenson
Copy link

@valentinedwv

Is this issue related? #7434

Thanks!

@valentinedwv
Copy link
Author

Think #7960 sounds closer.
Maybe that services>container image "field' is not being updated.

@tamarahenson
Copy link

@valentinedwv

I wanted to follow up on this request. When you deploy in Portainer, you point to the repository and branch. Portainer can only see that branch. Can you confirm you made changes in that branch?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants