{"action":"created","issue":{"url":"https://api.github.com/repos/nodesource/docker-node/issues/39","labels_url":"https://api.github.com/repos/nodesource/docker-node/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/nodesource/docker-node/issues/39/comments","events_url":"https://api.github.com/repos/nodesource/docker-node/issues/39/events","html_url":"https://github.com/nodesource/docker-node/issues/39","id":120395885,"number":39,"title":"Node v5.1.1, v4.2.3, v0.12.9, v0.10.41","user":{"login":"billinghamj","id":905772,"avatar_url":"https://avatars.githubusercontent.com/u/905772?v=3","gravatar_id":"","url":"https://api.github.com/users/billinghamj","html_url":"https://github.com/billinghamj","followers_url":"https://api.github.com/users/billinghamj/followers","following_url":"https://api.github.com/users/billinghamj/following{/other_user}","gists_url":"https://api.github.com/users/billinghamj/gists{/gist_id}","starred_url":"https://api.github.com/users/billinghamj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/billinghamj/subscriptions","organizations_url":"https://api.github.com/users/billinghamj/orgs","repos_url":"https://api.github.com/users/billinghamj/repos","events_url":"https://api.github.com/users/billinghamj/events{/privacy}","received_events_url":"https://api.github.com/users/billinghamj/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-12-04T12:51:51Z","updated_at":"2015-12-10T20:54:39Z","closed_at":"2015-12-09T19:27:35Z","body":"4 new versions of Node were released today to resolve various security issues in OpenSSL, V8 and Node itself.\r\n\r\nCould you add these to Docker Hub please?\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/nodesource/docker-node/issues/comments/163746502","html_url":"https://github.com/nodesource/docker-node/issues/39#issuecomment-163746502","issue_url":"https://api.github.com/repos/nodesource/docker-node/issues/39","id":163746502,"user":{"login":"wblankenship","id":1081565,"avatar_url":"https://avatars.githubusercontent.com/u/1081565?v=3","gravatar_id":"","url":"https://api.github.com/users/wblankenship","html_url":"https://github.com/wblankenship","followers_url":"https://api.github.com/users/wblankenship/followers","following_url":"https://api.github.com/users/wblankenship/following{/other_user}","gists_url":"https://api.github.com/users/wblankenship/gists{/gist_id}","starred_url":"https://api.github.com/users/wblankenship/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wblankenship/subscriptions","organizations_url":"https://api.github.com/users/wblankenship/orgs","repos_url":"https://api.github.com/users/wblankenship/repos","events_url":"https://api.github.com/users/wblankenship/events{/privacy}","received_events_url":"https://api.github.com/users/wblankenship/received_events","type":"User","site_admin":false},"created_at":"2015-12-10T20:54:39Z","updated_at":"2015-12-10T20:54:39Z","body":"@xmikus01 I'll break this up into two parts, both of which are super weird.\r\n\r\nPart 1: Not having an update for 4\r\n\r\nThe 4[.2[.3]] values were updated in the automated build settings. I just visually verified:\r\n\r\n![](https://cloud.githubusercontent.com/assets/1081565/11728006/6023c4a4-9f55-11e5-9f2b-8fdf3c39d32d.png)\r\n\r\nI also have a tool that verifies this for me (since I can't get an API to automate the updates). When dealing with 400+ Docker images each with several aliases, human error causes quite a bit of drift so I don't trust myself to maintain it by hand. https://github.com/nodesource/docker-node/blob/master/tools/registry_diff.js\r\n\r\nI pulled down `nodesource/trusty:4` and can confirm that it is 4.2.3\r\n\r\n![](https://cloud.githubusercontent.com/assets/1081565/11728089/d01c9182-9f55-11e5-8b44-9b6f590cd859.png)\r\n\r\nThat being said, this wouldn't be the first time the Docker Registry didn't properly update a tag. We are considering dropping the Automated Build tag and uploading our own build logs and pushing our own images (we generate thorough logs every-time we run our integration tests).\r\n\r\nPart 2: Digest not matching\r\n\r\nI have rarely been able to get the digests to match on Automated Builds, even when the Dockerfiles are aliases. I think the culprit is the `apt-get` commands, and the downloads not being deterministic enough (perhaps timestamps?) to generate an identical hash.\r\n\r\nAgain, this would be solved by dropping the Automated Build status.\r\n\r\nI hope to propose a better solution for all of this in the coming weeks."}}