{"action":"created","issue":{"url":"https://api.github.com/repos/docker/machine/issues/3358","repository_url":"https://api.github.com/repos/docker/machine","labels_url":"https://api.github.com/repos/docker/machine/issues/3358/labels{/name}","comments_url":"https://api.github.com/repos/docker/machine/issues/3358/comments","events_url":"https://api.github.com/repos/docker/machine/issues/3358/events","html_url":"https://github.com/docker/machine/issues/3358","id":150285509,"number":3358,"title":"Digital ocean driver create command fails on new ubuntu 16.04 LTS image","user":{"login":"raarts","id":3168197,"avatar_url":"https://avatars.githubusercontent.com/u/3168197?v=3","gravatar_id":"","url":"https://api.github.com/users/raarts","html_url":"https://github.com/raarts","followers_url":"https://api.github.com/users/raarts/followers","following_url":"https://api.github.com/users/raarts/following{/other_user}","gists_url":"https://api.github.com/users/raarts/gists{/gist_id}","starred_url":"https://api.github.com/users/raarts/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raarts/subscriptions","organizations_url":"https://api.github.com/users/raarts/orgs","repos_url":"https://api.github.com/users/raarts/repos","events_url":"https://api.github.com/users/raarts/events{/privacy}","received_events_url":"https://api.github.com/users/raarts/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2016-04-22T06:51:33Z","updated_at":"2016-05-05T22:33:11Z","closed_at":null,"body":"```\r\n$ docker-machine create -d digitalocean --digitalocean-access-token xxx --digitalocean-ssh-key-fingerprint xxx --digitalocean-image ubuntu-16-04-x64  test-machine\r\nRunning pre-create checks...\r\nCreating machine...\r\n(test-machine) Creating SSH key...\r\n(test-machine) Creating Digital Ocean droplet...\r\n(test-machine) Waiting for IP address to be assigned to the Droplet...\r\nWaiting for machine to be running, this may take a few minutes...\r\nDetecting operating system of created instance...\r\nWaiting for SSH to be available...\r\nDetecting the provisioner...\r\nProvisioning with ubuntu(systemd)...\r\nError creating machine: Error running provisioning: Something went wrong running an SSH command!\r\ncommand : sudo apt-get update\r\nerr     : exit status 100\r\noutput  : Reading package lists...\r\nE: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)\r\nE: Unable to lock directory /var/lib/apt/lists/\r\n```"},"comment":{"url":"https://api.github.com/repos/docker/machine/issues/comments/217299028","html_url":"https://github.com/docker/machine/issues/3358#issuecomment-217299028","issue_url":"https://api.github.com/repos/docker/machine/issues/3358","id":217299028,"user":{"login":"nathanleclaire","id":1476820,"avatar_url":"https://avatars.githubusercontent.com/u/1476820?v=3","gravatar_id":"","url":"https://api.github.com/users/nathanleclaire","html_url":"https://github.com/nathanleclaire","followers_url":"https://api.github.com/users/nathanleclaire/followers","following_url":"https://api.github.com/users/nathanleclaire/following{/other_user}","gists_url":"https://api.github.com/users/nathanleclaire/gists{/gist_id}","starred_url":"https://api.github.com/users/nathanleclaire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nathanleclaire/subscriptions","organizations_url":"https://api.github.com/users/nathanleclaire/orgs","repos_url":"https://api.github.com/users/nathanleclaire/repos","events_url":"https://api.github.com/users/nathanleclaire/events{/privacy}","received_events_url":"https://api.github.com/users/nathanleclaire/received_events","type":"User","site_admin":false},"created_at":"2016-05-05T22:33:11Z","updated_at":"2016-05-05T22:33:11Z","body":"> Why not wait for /var/lib/apt/lists/lock to disappear?\r\n\r\nJust off the top of my head, it's a bit fragile as a solution.  You have no real guarantee that's going to disappear in any reasonable amount of time, if an `apt` process aborts in the middle it will still be around and never get cleaned up, forcing us to introduce additional timeouts around this, and so on.  It would be far better to handle in `apt` itself if possible, and/or establish what exactly DO are doing behind the scenes that's causing this before implementing anything to try and fix it."}}