starred/docker-ipsec-vpn-server
1
0
Fork 0
mirror of https://github.com/hwdsl2/docker-ipsec-vpn-server.git synced 2026-04-26 10:05:48 +03:00
Code Issues Projects Releases Packages Wiki Activity

[GH-ISSUE #98] Tags for Older Version #85

New issue
Closed
opened 2026-03-02 07:11:36 +03:00 by kerem · 5 comments
kerem commented 2026-03-02 07:11:36 +03:00
Owner
Copy link

Originally created by @pogzie on GitHub (Nov 12, 2018).
Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/98

Hi, since I was having problems with the new build, I was checking if there were other older versions available in Dockerhub, but all I see is the latest version.

Possible to keep the old releases for when the new version fails to work properly?

Originally created by @pogzie on GitHub (Nov 12, 2018). Original GitHub issue: https://github.com/hwdsl2/docker-ipsec-vpn-server/issues/98 Hi, since I was having problems with the new build, I was checking if there were other older versions available in Dockerhub, but all I see is the latest version. Possible to keep the old releases for when the new version fails to work properly?
kerem closed this issue 2026-03-02 07:11:36 +03:00
kerem commented 2026-03-02 07:11:37 +03:00
Author
Owner
Copy link

@selim13 commented on GitHub (Jan 22, 2019):

Not sure why this issue was closed.
It would be really nice to see proper tagging/versioning of the image.

<!-- gh-comment-id:456322406 --> @selim13 commented on GitHub (Jan 22, 2019): Not sure why this issue was closed. It would be really nice to see proper tagging/versioning of the image.
kerem commented 2026-03-02 07:11:37 +03:00
Author
Owner
Copy link

@hwdsl2 commented on GitHub (Jan 22, 2019):

@selim13 Thanks for the suggestion. What is your use case for tagging this image? And what would you suggest that the tags are based on? Libreswan versions?

<!-- gh-comment-id:456324439 --> @hwdsl2 commented on GitHub (Jan 22, 2019): @selim13 Thanks for the suggestion. What is your use case for tagging this image? And what would you suggest that the tags are based on? Libreswan versions?
kerem commented 2026-03-02 07:11:37 +03:00
Author
Owner
Copy link

@selim13 commented on GitHub (Jan 22, 2019):

What is your use case for tagging this image?

It's a good practice to keep image version pinned inside docker-compose file to prevent things breaking on images pulls. Also with github tagging/releases it is easier to keep track on source changes between them (especially on "sensitive" type of image like vpn). And it is simple to setup automated builds from those tags.

And what would you suggest that the tags are based on? Libreswan versions?

I would suggest libreswan version + numeric postfix like "3.27-1" as there is more interest on versioning image build scripts aside from libreswan.

Thanks for your time and this handy image =)

<!-- gh-comment-id:456346379 --> @selim13 commented on GitHub (Jan 22, 2019): > What is your use case for tagging this image? It's a good practice to keep image version pinned inside docker-compose file to prevent things breaking on images pulls. Also with github tagging/releases it is easier to keep track on source changes between them (especially on "sensitive" type of image like vpn). And it is simple to setup automated builds from those tags. > And what would you suggest that the tags are based on? Libreswan versions? I would suggest libreswan version + numeric postfix like "3.27-1" as there is more interest on versioning image build scripts aside from libreswan. Thanks for your time and this handy image =)
kerem commented 2026-03-02 07:11:37 +03:00
Author
Owner
Copy link

@rasodu commented on GitHub (Jul 27, 2020):

Not sure how much complexity it would add to current build process, but having tags have a few advantages.

  • Allow testing of the image per-production environment before deploying it in production.
  • Rollback if someone is having problem in production. Some time not all the users see bugs. A specific configuration could be causing the issue. It would be good to be able to rollback to previously working release.
  • If we ever need to release backward incompatible release(Let's say env variables name changes or add a new required env), then people who don't make change can still keep the installation working by using the tag under which their installed works.
<!-- gh-comment-id:664079898 --> @rasodu commented on GitHub (Jul 27, 2020): Not sure how much complexity it would add to current build process, but having tags have a few advantages. - Allow testing of the image per-production environment before deploying it in production. - Rollback if someone is having problem in production. Some time not all the users see bugs. A specific configuration could be causing the issue. It would be good to be able to rollback to previously working release. - If we ever need to release backward incompatible release(Let's say env variables name changes or add a new required env), then people who don't make change can still keep the installation working by using the tag under which their installed works.
kerem commented 2026-03-02 07:11:38 +03:00
Author
Owner
Copy link

@hwdsl2 commented on GitHub (Jul 27, 2020):

@rasodu Thank you for the suggestions. I agree that using tags may be beneficial in certain cases. However, for this particular Docker image, the testing in pre-production and/or rollback scenarios may not apply. And backward incompatible changes have been very rare in the history of this project. If you have examples of specific commit(s) which broke backward compatibility or could otherwise benefit from the use of tags, let me know.

<!-- gh-comment-id:664083671 --> @hwdsl2 commented on GitHub (Jul 27, 2020): @rasodu Thank you for the suggestions. I agree that using tags may be beneficial in certain cases. However, for this particular Docker image, the testing in pre-production and/or rollback scenarios may not apply. And backward incompatible changes have been very rare in the history of this project. If you have examples of specific commit(s) which broke backward compatibility or could otherwise benefit from the use of tags, let me know.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
bug

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question
No labels
bug
pull-request
question
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-ipsec-vpn-server#85
No description provided.