{"action":"created","issue":{"url":"https://api.github.com/repos/mailcow/mailcow-dockerized/issues/520","repository_url":"https://api.github.com/repos/mailcow/mailcow-dockerized","labels_url":"https://api.github.com/repos/mailcow/mailcow-dockerized/issues/520/labels{/name}","comments_url":"https://api.github.com/repos/mailcow/mailcow-dockerized/issues/520/comments","events_url":"https://api.github.com/repos/mailcow/mailcow-dockerized/issues/520/events","html_url":"https://github.com/mailcow/mailcow-dockerized/issues/520","id":251584960,"number":520,"title":"QUESTION: It is safe to use :latest instead","user":{"login":"jodumont","id":5204724,"avatar_url":"https://avatars3.githubusercontent.com/u/5204724?v=4","gravatar_id":"","url":"https://api.github.com/users/jodumont","html_url":"https://github.com/jodumont","followers_url":"https://api.github.com/users/jodumont/followers","following_url":"https://api.github.com/users/jodumont/following{/other_user}","gists_url":"https://api.github.com/users/jodumont/gists{/gist_id}","starred_url":"https://api.github.com/users/jodumont/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jodumont/subscriptions","organizations_url":"https://api.github.com/users/jodumont/orgs","repos_url":"https://api.github.com/users/jodumont/repos","events_url":"https://api.github.com/users/jodumont/events{/privacy}","received_events_url":"https://api.github.com/users/jodumont/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-08-21T08:28:31Z","updated_at":"2017-08-21T20:00:30Z","closed_at":null,"body":"in reference of #340 \r\nI was wondering if it's safe to use :latest instead of version into the docker-compose.yml\r\nI know the docker best practice say : You must use version number\r\nPut in fact; most of the time is just more manipulation and potential error when you upgrade.\r\n\r\nSo It is safe to use :latest ?\r\n\r\nRegards!\r\n\r\nJonathan"},"comment":{"url":"https://api.github.com/repos/mailcow/mailcow-dockerized/issues/comments/323837949","html_url":"https://github.com/mailcow/mailcow-dockerized/issues/520#issuecomment-323837949","issue_url":"https://api.github.com/repos/mailcow/mailcow-dockerized/issues/520","id":323837949,"user":{"login":"mkuron","id":1748330,"avatar_url":"https://avatars0.githubusercontent.com/u/1748330?v=4","gravatar_id":"","url":"https://api.github.com/users/mkuron","html_url":"https://github.com/mkuron","followers_url":"https://api.github.com/users/mkuron/followers","following_url":"https://api.github.com/users/mkuron/following{/other_user}","gists_url":"https://api.github.com/users/mkuron/gists{/gist_id}","starred_url":"https://api.github.com/users/mkuron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mkuron/subscriptions","organizations_url":"https://api.github.com/users/mkuron/orgs","repos_url":"https://api.github.com/users/mkuron/repos","events_url":"https://api.github.com/users/mkuron/events{/privacy}","received_events_url":"https://api.github.com/users/mkuron/received_events","type":"User","site_admin":false},"created_at":"2017-08-21T20:00:30Z","updated_at":"2017-08-21T20:00:30Z","body":"It is not safe to do that. The version numbers were explicitly added to make sure that the container always matches up with the configuration files in the Git repo. Running a newer container with an old Git repository was a very common source of error (just look through the issue tracker) that has gone away completely since switching to version numbers.\r\n\r\nOf course, requiring Mailcow to be run out of the Git repository (and not via a simple `docker pull`) is not exactly best practice, but it's the only viable way to maintain the complex interdependencies of a mail server."}}
{"actor":{"display_login":"mkuron"}}