Skip to main content
๐ŸŽ“ Claude Code Masterclass Learn AI-assisted development on Udemy โ€” plus the companion book on Leanpub & Amazon. Start Learning
Fix Ansible apt Module Lock Error on Ubuntu
Automation

Fix Ansible apt Module Lock Error on Ubuntu

How to fix the Could not get lock /var/lib/dpkg/lock error in Ansible. Causes, diagnosis, and solutions with working examples.

LB
Luca Berton
ยท 1 min read

If you are seeing Could not get lock /var/lib/dpkg/lock when running Ansible, here is how to fix it.

What This Error Means

Another process holds the dpkg lock. Wait for unattended-upgrades to finish or kill the blocking process.

Quick Diagnosis

# Run with verbose output
ansible-playbook playbook.yml -vvv

# Syntax check first
ansible-playbook playbook.yml --syntax-check

# Check in dry-run mode
ansible-playbook playbook.yml --check --diff

How to Fix It

Step 1: Identify the Root Cause

The -vvv output will show you exactly where the error occurs and what went wrong.

Step 2: Apply the Fix

Another process holds the dpkg lock. Wait for unattended-upgrades to finish or kill the blocking process.

Review your playbook, inventory, and variable files. Test with --check before applying.

Step 3: Verify

# Run again and confirm no errors
ansible-playbook playbook.yml

# Should complete with 0 failures

Prevention Tips

  • Always use --syntax-check before running playbooks
  • Use ansible-lint to catch common mistakes
  • Test with Molecule before deploying to production
  • Use FQCNs (Fully Qualified Collection Names) for all modules
  • Keep Ansible and collections updated

Free 30-min AI & Cloud consultation

Book Now