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: latest tag not defined #434

Open
psiinon opened this issue May 30, 2023 · 3 comments
Open

Docker: latest tag not defined #434

psiinon opened this issue May 30, 2023 · 3 comments

Comments

@psiinon
Copy link

psiinon commented May 30, 2023

Describe the bug
It is not possible to pull the latest version from docker without knowing exactly which version to use. Which is a complete pain and kind of misses the point of docker 😉

To Reproduce
Steps to reproduce the behavior:

  1. From the command line run: docker pull sasanlabs/owasp-vulnerableapp
  2. See error:
Using default tag: latest
Error response from daemon: manifest for sasanlabs/owasp-vulnerableapp:latest not found: manifest unknown: manifest unknown

Note that this is the exact command specified on https://hub.docker.com/r/sasanlabs/owasp-vulnerableapp

Expected behavior
The latest version of the app should be downloaded

Additional context
Specifying the exact version works, e.g. : docker pull sasanlabs/owasp-vulnerableapp:1.11.22

Would you like to help fix this issue?
Just say if you'd like to try and help fix this issue. We'll provide any advice and guidance you need.

Hopefully there will be a quick fix for this so you wont need my help, but if I can help then just ping me :)

psiinon added a commit to psiinon/zap-mgmt-scripts that referenced this issue May 30, 2023
Pending a fix to SasanLabs/VulnerableApp#434

Signed-off-by: Simon Bennetts <[email protected]>
psiinon added a commit to psiinon/zap-mgmt-scripts that referenced this issue May 30, 2023
Pending a fix to SasanLabs/VulnerableApp#434

Signed-off-by: Simon Bennetts <[email protected]>
@preetkaran20
Copy link
Member

@psiinon we have removed latest tag a few months ago and major reason for that is docker pull not pulling latest changes. So what happens is that once we release latest tag, users who already have downloaded the latest tag will not get the newer updates until they don't remove the image from there local machine/host machine.

However, I think we can push latest image for now considering default behavior of docker pull of fetching latest tags

@NaveenPaulBosco
Copy link

I see this issue is still open. I am interested in this project and contributing to it. Please assign a good first issue to me to work on. Thank you!

@preetkaran20
Copy link
Member

Thanks a lot @NaveenPaulBosco. I would suggest to go through the issues section and pick any issue labeled with good first issue.

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

3 participants