Lego: Tags on docker automated builds

Created on 17 Sep 2018  路  4Comments  路  Source: go-acme/lego

Hi there!

First awesome job on this. This is a great project!

I noticed that you only build the docker container from master in your automated builds on the docker hub. I'm using your docker container and I've had some of my things break in the last few days due to unexpected update.

If you set it up like on the screenshot below you can have

  • images from git tag tagged as the git tag => e.g. xenolf/lego:v1.0.1
  • images from latest git tag tagged as "latest"
  • images from master branch tagged as dev

screen shot 2018-09-17 at 11 27 41 am

Let me know if you have any question. You can also add me as a contributor on your hub repo if you want me to set it up => https://hub.docker.com/u/kuuji/

Most helpful comment

Done. Should be fine in a few minutes.

All 4 comments

@xenolf? Do you think you could add the mentioned configuration?

I configured it as seen in the picture but I don't know how long it will take for it to refresh.

@xenolf It will only work going forward. If you want to create images from existing tags you need to enable build triggers at the bottom of the build settings page, then you can trigger them like this

curl -H "Content-Type: application/json" --data '{"source_type": "Tag", "source_name": "v0.5.0"}' -X POST <your_trigger_url>

You'll need to replace <your_trigger_url> by what's in the docker interface and set the source_name appropriately.

I'd recommend doing v0.5.0 v1.0.0 and v1.0.1 in that order, since the last one is always going to trigger a "latest" tag.

Done. Should be fine in a few minutes.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mholt picture mholt  路  3Comments

bouwerp picture bouwerp  路  3Comments

richtr picture richtr  路  5Comments

onlyjob picture onlyjob  路  3Comments

rawtaz picture rawtaz  路  3Comments