How do I push a vew version instead of adding a new Tag? #59312
Replies: 2 comments 2 replies
-
Hello and good day @htt-eroldan Docker doesn’t have a built-in versioning mechanism, but you can use tags to represent different versions of your images. That should work. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi!
I'm triying to follow this instructions to push a new version of an existing Docker image in my packages.
But instead I can only add a new Tag to the existing version.
In my code I'm logging in
const login = 'echo $DOCKER_PASSWORD | docker login ghcr.io -u $DOCKER_USERNAME --password-stdin'
child.execSync(login, { env });
and pushing with
const push = 'docker push ghcr.io/${company}/${package}:${newVersion}'
child.execSync(push, { cwd: folder });
According to the documentation I shoud be pushing a new version of the package, but I find that, after those actions, my package has only a new tag instead of a vew version.
Is there any problem with docker packages?
Someone can help me with this?
Beta Was this translation helpful? Give feedback.
All reactions