Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.
Sign up to join this community
On an embedded system with a very limited disk space I have the folder /var/cache/apt full with some 700MB of srcpkgcache.bin.* and a couple of large *.bin files.
Performing sudo apt-get clean did not make a visible difference.
Is it safe to manually delete these *.bin* files?
Not really. Those files help your system determine what is available and what isn't. Emptying that directory will result in a broken apt-get system. Here are a couple of tips.
First, auto clean
add a
DPkg::Post-Invoke { "apt-get clean"; };
to the end of /etc/apt/apt.conf. It will make apt and dpkg processes take longer, but will make it so your cache directory is always clean.
Next, Remove archives
Start by removing and disabling all source archives (that your not using). On an embedded system you likely don't need them. Next remove all the archives that are not in use. You can run apt-cache policy to figure out what repo a package is coming from if your not sure.
More Removal of archives
Some PPAs are horrid about having huge number of packages in them when you only need 1 or 2. Try disabling those PPAs and just installing the deb files manually. You save space in those cases, but you loose auto update. Keep in mind that dpkg will handle dependencies, so you can still install thing-with-tons-of-deps.deb then run apt-get -f install to fetch the dependencies.
Totally Extreme Answer 1
Because were talking about an embedded system, 90% of the main repos won't do you any good. To handel this you could run your own apt-get repo server See this link. It's not easy, and it's a PIA for just one machine. But if you have several of these machines it's totally worth it. (You apt repo server can host just a subset of packages that you actually use. You don't need to mirror the whole thing)
Totally Extreme Answer 2
If space is really that large of an issue, then you can disable apt all together and revert to manually installing via dpkg. I have had to do this on several embedded systems. It works, but it's an admin nightmare.
*.bin files? Any run of apt-get update will regenerate those files from scratch (tested). For example my use case is that I want to create LXC container templates and want to strip the archive down as much as possible. I cannot see any reason ho it's unsafe. And your answer doesn't indicate a reason, just states that it is unsafe. Tested that it's perfectly safe on Ubuntu 14.04.
Jun 1, 2015 at 15:48
apt-cache clean in a dpkg call will result in cleaner cache, but user says apt-cache clean didn't clean anything for them. Also your answer is totally wrong because dpkg doesn't use /var/cache/apt/* content to get informed for package statistic.
clean as * clean clears out the local repository of retrieved package files. It removes everything but the lock file from /var/cache/apt/archives/ and /var/cache/apt/archives/partial/.* If it is dangerous, there would be no such function to clean.
You can of course delete pkgcache.bin and srcpkgcache.bin, nothing happens. Just run apt-get update to re-create them.
.deb files?
Jan 2, 2018 at 23:07
Keep the pkgcache.bin and srcpkgcache.bin, you can safely delete the others. Don't touch the directories!
*bin.* files to a backup folder. However, why does apt-get manages the cache inside the cache? A cache directory should be a temporary storage by nature.
You can of course create a NFS-share (network filesystem) for this. Leave these files on a server and mount the share only when you want to update/install packages. In embedded environments, the installation will usually be relatively static anyway.
sshfs is another good option, is much easier to set up (basically only requires SSH which is standard), but it has more overhead (slower).
*.binfiles in said folder - assuming no apt-related process is currently running. The nextapt-get updatewill regenerate the*.binfiles. This question is decidedly not about the files in/var/cache/apt/archives, but the files/var/cache/apt/*.bin. Big difference. The former can be cleaned by issuingapt-get clean, the latter has to be manually removed. Clearly those voting to close the question have not read the question properly. Unfortunately I cannot vote to reopen after awarding some of my rep in bounties.archiveswithin/var/cache/apt/, this one is about the*.bin*files.