{"action":"created","issue":{"url":"https://api.github.com/repos/sysrepo/sysrepo/issues/404","repository_url":"https://api.github.com/repos/sysrepo/sysrepo","labels_url":"https://api.github.com/repos/sysrepo/sysrepo/issues/404/labels{/name}","comments_url":"https://api.github.com/repos/sysrepo/sysrepo/issues/404/comments","events_url":"https://api.github.com/repos/sysrepo/sysrepo/issues/404/events","html_url":"https://github.com/sysrepo/sysrepo/issues/404","id":182223860,"number":404,"title":"Docker image tag guidelines","user":{"login":"plajjan","id":841628,"avatar_url":"https://avatars.githubusercontent.com/u/841628?v=3","gravatar_id":"","url":"https://api.github.com/users/plajjan","html_url":"https://github.com/plajjan","followers_url":"https://api.github.com/users/plajjan/followers","following_url":"https://api.github.com/users/plajjan/following{/other_user}","gists_url":"https://api.github.com/users/plajjan/gists{/gist_id}","starred_url":"https://api.github.com/users/plajjan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/plajjan/subscriptions","organizations_url":"https://api.github.com/users/plajjan/orgs","repos_url":"https://api.github.com/users/plajjan/repos","events_url":"https://api.github.com/users/plajjan/events{/privacy}","received_events_url":"https://api.github.com/users/plajjan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-10-11T10:02:02Z","updated_at":"2016-10-14T10:32:38Z","closed_at":null,"body":"Hehe, I was about to open an issue on this a couple of days ago and wanted to suggest that we make the sysrepo-netopeer2 docker image build automatically.. but it seems it does already -yay \\o/\r\n\r\nI wonder from what though since there's no Dockerfile on this repo. Since automatically built, shouldn't it be built from this git repo so we actually get the latest changes?\r\n\r\nSecondly, I would like to understand which tag is used for what. In the past I've seen these devel_201610xx images and honestly I'm not too keen on that structure.\r\n\r\nI do think the git tags (v0.4.0 for example) should map to a docker image.\r\n\r\nQuestion is what \"latest\" (which is the default you get when you pull a docker image) should point to? git master? This would make latest a moving target, so when someone complains about a bug in :latest we need the SHA sum of the image rather than it's tag name. Should we even bother with daily devel builds?\r\n\r\nThoughts?"},"comment":{"url":"https://api.github.com/repos/sysrepo/sysrepo/issues/comments/253765772","html_url":"https://github.com/sysrepo/sysrepo/issues/404#issuecomment-253765772","issue_url":"https://api.github.com/repos/sysrepo/sysrepo/issues/404","id":253765772,"user":{"login":"rastislavszabo","id":15926980,"avatar_url":"https://avatars.githubusercontent.com/u/15926980?v=3","gravatar_id":"","url":"https://api.github.com/users/rastislavszabo","html_url":"https://github.com/rastislavszabo","followers_url":"https://api.github.com/users/rastislavszabo/followers","following_url":"https://api.github.com/users/rastislavszabo/following{/other_user}","gists_url":"https://api.github.com/users/rastislavszabo/gists{/gist_id}","starred_url":"https://api.github.com/users/rastislavszabo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rastislavszabo/subscriptions","organizations_url":"https://api.github.com/users/rastislavszabo/orgs","repos_url":"https://api.github.com/users/rastislavszabo/repos","events_url":"https://api.github.com/users/rastislavszabo/events{/privacy}","received_events_url":"https://api.github.com/users/rastislavszabo/received_events","type":"User","site_admin":false},"created_at":"2016-10-14T10:32:38Z","updated_at":"2016-10-14T10:32:38Z","body":"Yes, we do have a similar setup up & running for sysrepo/sysrepo docker image: https://hub.docker.com/r/sysrepo/sysrepo/tags/ (including version tags that will be automatically added starting from the next version).\r\n\r\nBut tags from sysrepo/sysrepo do not automatically propagate to sysrepo/sysrepo-netopeer2. To only thing that I'm able to setup on dockerhub is that any rebuild of sysrepo/systrepo triggers rebuild of sysrepo/netopeer2:latest."}}
{"actor":{"display_login":"rastislavszabo"}}