root@01f1d013bd74: /opt/intel/computer_vision_sdk_2018.3.343/deployment_tools/inference_engine/samples# sudo apt-get install cmake

E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

marked as duplicate by RoVo, guiverc, karel, Community Aug 30 at 8:45

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 2
    Why do you post a question which is an exact duplicate of another question here (the fifth-most upvoted question of all times) and then answer your own question after one minute with a long (and complicated) answer? – RoVo Aug 30 at 7:15
  • okk , i will never do that again , i stuck in a project many problem so i post it and i am new in stack overflow ,it is tough to understand it . – Ankit gupta Aug 30 at 8:44

i solve from problem using this website :: https://www.tecmint.com/fix-unable-to-lock-the-administration-directory-var-lib-dpkg-lock/

  1. Find and Kill all apt-get or apt Processes

Run the command below to generate a list of all processes whose name comprises of the word apt, you will get a list inclusive of all apt or apt-get processes by using ps and grep commands together with a pipeline.

$ ps -A | grep apt

Find apt and apt-get Processes

Find apt and apt-get Processes

For each apt-get or apt process that you can see in the output of the command above, kill each process using the command below.

The process ID (PID) is found in the first column from the screenshot above.

$ sudo kill -9 processnumber OR $ sudo kill -SIGKILL processnumber

For instance, in the command below where 9 is the signal number for the SIGKILL signal, will kill the first apt process:

$ sudo kill -9 13431 OR $ sudo kill -SIGKILL 13431

  1. Delete the lock Files

A lock file simply prevents access to another file(s) or some data on your Linux system, this concept is present in Windows and other operating systems as well.

Once you run an apt-get or apt command, a lock file is created under the any of these directories /var/lib/apt/lists/, /var/lib/dpkg/ and /var/cache/apt/archives/.

This helps to avoid the apt-get or apt process that is already running from being interrupted by either a user or other system processes that would need to work with files being used by apt-get or apt. When the process has finished executing, the lock file is then deleted.

Important: In case a lock is still exiting in the two directories above with no noticeable apt-get or apt process running, this may mean the process was held for one reason or the other, therefore you need to delete the lock files in order to clear the error.

First execute the command below to remove the lock file in the /var/lib/dpkg/ directory:

$ sudo rm /var/lib/dpkg/lock

Afterwards force package(s) to reconfigure like so:

$ sudo dpkg --configure -a

Alternatively, delete the lock files in the /var/lib/apt/lists/ and cache directory as below:

$ sudo rm /var/lib/apt/lists/lock $ sudo rm /var/cache/apt/archives/lock

Next, update your packages sources list as follows:

$ sudo apt update OR $ sudo apt-get update

In conclusion, we have walked through two important methods to deal with a common problem faced by Ubuntu (and its derivatives) users, while running apt-get or apt as well as aptitude commands.

Do you have any other reliable methods to share meant for deal with this common error? Then get in touch with us via the feedback form below.

In addition, you may as well want to learn how to find and kill running processes and read through a simple guide to kill, pkill and killall commands to terminate a process in Linux.

Not the answer you're looking for? Browse other questions tagged or ask your own question.