{"id":646,"date":"2018-05-28T18:12:24","date_gmt":"2018-05-28T18:12:24","guid":{"rendered":"http:\/\/camilalui.com\/?p=646"},"modified":"2019-06-30T16:07:35","modified_gmt":"2019-06-30T16:07:35","slug":"646","status":"publish","type":"post","link":"https:\/\/camilalui.com\/?p=646","title":{"rendered":"Ubuntu with \/var\/lib\/dpkg locked"},"content":{"rendered":"

Error:<\/strong>
\n“Could not get lock \/var\/lib\/dpkg\/lock – open (11: Resource temporarily unavailable)”<\/p>\n

As soon as you have your Ubuntu 16.04 machine up provisioned by either Ansible or Vagrant, it starts a process for unattended-updates that locks the dpkg repository and any script that needs to send instructions for apt app, will fail.<\/p>\n

This appears to be caused by a combination of an unattended-upgraded package policy set by the Debian\/Ubuntu, and a change in how unattended upgrades are handled now.<\/p>\n

In past versions of Ubuntu, unattended package upgrades were handled by creating a cron job in \/etc\/cron.daily responsible for running apt. With 16.04 version and the shift to systemd, unattended upgrades are handled by a systemd unit. The new systemd unit has OnCalendar set to 6am and 6pm, along with Persistent set to true. The result is that a full apt-get update && apt-get upgrade will run the first time the system boots, in order to “catch-up” with missed runs.<\/p>\n

The idea that packages will be upgraded automatically twice a day, so what you can do is to disable the automatic apt upgrades at all.
\n
\nHow to disable apt automatic updates:
\n<\/strong><\/p>\n

You have to edit this file:<\/p>\n

\n