Linux Cannot Read File Data Error 21
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 15 Star 152 Fork 55 SvenDowideit/dockerfiles Code Issues 16 Pull requests 3 Projects 0 Pulse Graphs New issue libapparmor.so.1: cannot open shared object file: No such file or directory
Libapparmor.so.1: Cannot Open Shared Object File: No Such File Or Directory
#17 Open kstenerud opened this Issue Sep 15, 2014 · 29 comments Projects None docker libapparmor yet Labels None yet Milestone No milestone Assignees No one assigned 17 participants kstenerud commented Sep 15, 2014 Not sure docker cannot open shared object file if this rates as a samba, docker, or ubuntu issue, but: # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2c93025ecbcf ubuntu:latest /bin/bash 11 seconds ago Up 11 seconds grave_sammet # docker run --rm -v
Error While Loading Shared Libraries: Cannot Open Shared Object File:
$(which docker):/docker -v /var/run/docker.sock:/docker.sock svendowideit/samba grave_sammet /docker: error while loading shared libraries: libapparmor.so.1: cannot open shared object file: No such file or directory Yet apparmor does exist: # ldconfig -v|grep apparmor libapparmor.so.1 -> libapparmor.so.1.1.0 Running on Ubuntu server 14.04. cdancy commented Oct 14, 2014 Have the same issue, using the same container, trying to pass the docker binary to the container. Have you found a workaround? cdancy commented Oct 14, 2014 I can confirm that
Ldconfig
testing under CentOS 7 (as host machine with ubuntu 14.04 as container) I get a similar issue though it's 'libdevmapper.so.1.02' that can't be loaded. clzhao commented Jul 16, 2015 @cdancy Have you got a solution for this problem ("I can confirm that testing under CentOS 7 (as host machine with ubuntu 14.04 as container) " ) , or you have tried other ways to do so? Hoping for your response. Thanks a lot ! cdancy commented Jul 16, 2015 @carlye566 no longer using centos7. Switched to arch linux, which is always updating to the latest version of docker, and have never seen this problem. I use RedHat7 at work, which should loosely mirror centos7, and I don't see the issue there either. clzhao commented Jul 16, 2015 @cdancy OK. Thank you all the same! tomfotherby commented Jul 27, 2015 I get this problem with Ubuntu 15.04 and docker v1.7.1 since I changed getting docker from the lxc-docker repo to the docker-engine repo (following the latest blog post (NEW APT AND YUM REPOS)) I can reproduce it using this command: $ docker run --rm -it \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /usr/bin/docker:/usr/bin/docker \ ubuntu docker --version > error while loading shared libraries: libapparmor.so.1: cannot open shared object file: No such file or directory (This runs a docker --version command but from within a ub
Discuss installing and running CINT here. Please post bug reports here. Moderator: cintdev docker inside docker Post Reply Search Advanced search First unread post • 40
Get Docker
posts 1 2 3 Next dsteele Posts: 23 Joined: Tue Mar 08, 2005 19:12 Location: docker jenkins Chicago, IL error while loading shared libraries Quote Unread postby dsteele » Mon Jan 09, 2006 19:29 I'm getting the following error trying to https://github.com/SvenDowideit/dockerfiles/issues/17 run rootcint: /usr/local/root/bin/rootcint: error while loading shared libraries: libCint.so.5.06: cannot open shared object file: No such file or directory make[1]: *** [out/root_dict.cpp] Error 127 The full command I'm using is: /usr/local/root/bin/rootcint -v -f out/root_dict.cpp -c -p -I../common/include -Iinclude -I. -D_OAWG -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D__extension__="" -D__attribute__\\\(X\\\)="" -D__const=const -D__restrict="" -D__signed=signed -D__volatile=volatile https://root.cern.ch/phpBB3/viewtopic.php?t=2921&start=30 -D__BEGIN_DECLS= -D__END_DECLS= -D__THROW= include/VAArrayInfo.h include/VAConfigurationData.h include/VACoordinateData.h include/VADataClasses.h include/VAParameterData.h include/VAPixelStatusData.h include/VAQStatsData.h include/VARelGainData.h include/VARootIO.h include/VARunHeader.h include/VAShowerData.h include/VASimulationDataClasses.h include/VATelescopeData.h include/VATime.h include/VATOffsetData.h include/LinkDef.h YES, I have $ROOTSYS/lib exported to my LD_LIBRARY_PATH. Any ideas what is wrong? Top pcanal Posts: 6984 Joined: Wed Aug 27, 2003 15:22 Location: Fermilab Quote Unread postby pcanal » Mon Jan 09, 2006 19:54 Did you check that there _is_ a file named /usr/local/root/lib/libCint.so.5.06? If there isn't then you install is not properly done. Philippe Top dsteele Posts: 23 Joined: Tue Mar 08, 2005 19:12 Location: Chicago, IL file exists Quote Unread postby dsteele » Mon Jan 09, 2006 19:56 Yes, the file exists and is non-empty. Top pcanal Posts: 6984 Joined: Wed Aug 27, 2003 15:22 Location: Fermilab Quote Unread postby pcanal » Mon Jan 09, 2006 20:00 What about permission? Do you user have read and execute permission to this file? Ph
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://serverfault.com/questions/289679/error-while-loading-shared-libraries-lib-libsepl-so-1-cannot-read-file-data more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges https://lonesysadmin.net/2013/02/22/error-while-loading-shared-libraries-cannot-open-shared-object-file/ Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error while loading shared libraries /lib/libsepl.so.1: cannot read file data up vote 0 cannot open down vote favorite I've created quite a predicament with my desktop installation and would prefer to be able to salvage it instead of having to reformat/re-install Ubuntu. Quite a lot happened and here's my best recollection: My Ubuntu installation stopped working and I could not get the desktop to load. I backup up my entire home directory by creating a zip file along with other small zip files. I used Alt + Del + F1 to get cannot open shared the CLI to do this. I then did different things trying to get the desktop to load. I did a apt-get upgrade, to try and get it to work; this was not sucessful. Working through several dependency issues I finally got sudo apt-get ubuntu-desktop upgrade to work, but it did not finish completely. I started to get out of memory errors. I am assuming this was because too much hard drive space was taken up by the zip files I had created -I could not boot and do anything properly after that. Every attempt to modify the filesystem (to free up space) results in an error "Read Only File System". The root file system was not being mounted and I would see root@none on the CL Looking on the boot loader I now have Ubuntu 9.10 2.6.24-generic installed I burnt a new installation of Ubuntu 10.4 LTS Using Live CD I tried to see if I could free up some space and get the system back to more stable state, however this was NOT sucessful. I tried to mount my drive by sudo mount -t ext3 but I keep getting the following error: error while loading shared libraries: /lib/libsepol.so.1: cannot read file data: Input/output error Does any one have any suggestions? It would be greatly appreciated! The only remaining option now I am looking at is a totaly re
comes a question from a Windows colleague trying to build software on Linux. He asks "I'm trying to do some web performance testing and I compiled weighttp and the libev libraries, which worked fine, but when I try to run the program it gives me the following error." weighttp: error while loading shared libraries: libev.so.4: cannot open shared object file: No such file or directory "I checked /usr/local/lib and the files are there. Do you have a suggestion?" Ah yes, a classic problem when building software. The problem here is that libev installed itself into /usr/local/lib: $ ls -l /usr/local/lib/libev* -rw-r--r--. 1 root root 435770 Feb 22 15:20 /usr/local/lib/libev.a -rwxr-xr-x. 1 root root 926 Feb 22 15:20 /usr/local/lib/libev.la lrwxrwxrwx. 1 root root 14 Feb 22 15:20 /usr/local/lib/libev.so -> libev.so.4.0.0 lrwxrwxrwx. 1 root root 14 Feb 22 15:20 /usr/local/lib/libev.so.4 -> libev.so.4.0.0 -rwxr-xr-x. 1 root root 174059 Feb 22 15:20 /usr/local/lib/libev.so.4.0.0 …but the dynamic linker doesn't know where they are, because it's never heard of /usr/local/lib. /usr/local is a traditional place for add-on software to install itself, so it doesn't interfere with the system libraries. If you're coming from a Windows background the .so files are essentially equal to DLLs, and load when you execute a program that depends on them. Programs that use dynamic libraries have several advantages, in that they're smaller, and the libraries can be updated without having to recompile all the programs that depend on them. So if there's a security problem with libev you can just patch libev, and not have to rebuild everything that uses that library. You can see what libraries a program is dynamically linked to with the ‘ldd' command: $ ldd /usr/local/bin/weighttp linux-vdso.so.1 => (0x00007fff251ff000) libev.so.4 => not found libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8f1cc1e000) libc.so.6 => /lib64/libc.so.6 (0x00007f8f1c88b000) /lib64/ld-linux-x86-64.so.2 (0x00007f8f1ce49000) That confirms we're just dealing with the new library, and not some other problem. Cool. Anyhow, there are five fixes that come to mind, and I'll group them into "terrible ideas" and "decent ideas." Of course, terrible and decent are my opinion, and your situation may dictate a different conclusion, so I'll add some commentary. If you're looking for the quickest way out skip to #5. Suboptimal Fixes/Terrible Ideas[0] 1. Install the libraries to /usr/lib instead of /usr/local/lib. I really don't like this because you're installing add-on software into a s