Not enough free space in /var/cache/apt/archives
-
Thanks for the tip @advocatux
I followed the instructions and I have a container working and I could install packages. -
Any solution to this? I don't want to use this workaround because I want to use the system as natively as possible. Ideally, I would prefer to not have unnecessary /dev/loop partitions in the first place.
-
sudo rm -r /var/cache/apt sudo tune2fs -m 0 /dev/loop0 -
@pparent This is not a good idea to do.
However, if one really needs to install debs in rootfs for some reason, such as using
ubports-qato test changes to system components from PRs, one can bind mount a directory in user writable partition on top of/var/cache/apt/archivesmkdir -p ~/aptcache sudo mount --bind /home/phablet/aptcache /var/cache/aptHowever, there will still be plenty of other issues if one wants to try to install from apt in rootfs, which is not supported, and it is strongly advised against doing so.
-
@pparent This is not a good idea to do.
No disrespect, but I think this is why I will choose pureOS in the long run, whenever I receive the phone and it is usable.
As users I want to be able to do the same things we can do on our computer, and be in control of our device, without being artificially limited, and not being sandboxed into a container. Otherwise I would use Android!
-
@pparent I think you will be somewhat disappointed by that too, because no matter what, the phone is still not a PC.
There is a huge difference between Android and UT. The way UT works is because it has to run on top of Android kernels, and because it is meant to provide a more secure alternative to Android, that does provide the ability to run legacy linux apps in a container too.
There are a whole lot of things about traditional PC Linux distros that just do not make sense to keep doing in the modern world, regardless of device. And pureOS isn't going to change that on their phone.
-
Actually I got the above problem trying to install a console program (dig) to do some in-field testing. To me all console programs make perfect sense being run on phones as they are on desktop, server, router, super-calculator, robot ... . And they can be used to really control the system.
On the other hand, on the graphical side, lately purism seems to make a great job adapting gnome apps for phone, so I guess we just have to wait and see.
-
@pparent said in Not enough free space in /var/cache/apt/archives:
Actually I got the above problem trying to install a console program (dig) to do some in-field testing. To me all console programs make perfect sense being run on phones as they are on desktop, server, router, super-calculator, robot ... . And they can be used to really control the system.
There is nothing preventing you from using CLI tools. Installing apps with legacy insecure packaging, is done in libertine. You can install and run whatever CLI apps you want, in there too.
But it doesn't change the facts.
-
@advocatux said in Not enough free space in /var/cache/apt/archives:
@gb making the system rw is not really a good idea for many reasons. If you want to use apt it's better to do it inside a contained environment, like Libertine for example.
Yes but I want to be able to use CLI tools on the real system to control the real system, control the machine, not be sandboxed in a container.
Can you explain what is insecure about "legacy packaging" (i.e apt ), and why it would be more insecure on the phone than it is on a laptop or a server?
-
I want to be able to use CLI tools on the real system to control the real system, control the machine, not be sandboxed in a container.
@pparent there's an official & supported way of doing things but of course you can do whatever you want with your device, you have complete freedom. Just don't expect any help when things go south
You can make the root filesystem
rw, you can resize partitions, you can use any repo or ppa that you want (as long as the packages are compiled for armhf), etc but you're at your own risk with that. -
@pparent said in Not enough free space in /var/cache/apt/archives:
Can you explain what is insecure about "legacy packaging" (i.e apt ), and why it would be more insecure on the phone than it is on a laptop or a server?
It is not truly secure on a laptop or server either. It has nothing to do with the device. With dpkg you are giving anyone who creates a package root access to your system, when you install that package.
As I've said many times before, phones are not PCs, and UT is not a traditional PC Linux distro. As @advocatux you are of course welcome to do whatever you want to your own device, with UT on it (it's yours, and UT is open source), but UT is not designed or built in this manner, and any changes you make are your own responsibility, and if installing updates break that (they will at some point), you will have deal with it yourself. If what you want is a traditional Linux distro on hardware that looks like a phone, there are other distributions working more towards that goal, such as postmarket OS. However, we are attempting to build a system usable for phones here, which is secure.
-
@dobey : This solution really helped for me to fix this issue
-
@dj said in Not enough free space in /var/cache/apt/archives:
@dobey : This solution really helped for me to fix this issue
Please, what solution?
-
Hi @rocky58
They were refering to this message:
https://forums.ubports.com/topic/1412/not-enough-free-space-in-var-cache-apt-archives/6When you see the "forward arrow" icon with the name of a user, there is a link to the actual message they replied to.
Hope it'll help and take note of Dobey's warnings.
-
@gb said in Not enough free space in /var/cache/apt/archives:
No solution yet
After 3 years, no solution yet?
-
Hi @vitalicus
You can wait 100 years it will be the same.
We do not support installation via APT or DPKG.The system is read only by design and the partition size depends on the initial partitions from the manufacturer AFAI K(now) or U(nderstand).
-
@ubtouch 16.04
sudo su root
mount -o remount rw /
cd /userdatadd bs=1M count=6000 if=/dev/zero of=system2.img
losetup -f --show system2.img
#return loop2
( loop0----system.img loop2----system2.img )dd if=/dev/loop0 of=/dev/loop2
resize2fs /dev/loop2
mv system.img system.old
mv system2.img system.imgreboot
#enjoy it
-
@Ben_Ben Just adding a note that this might result in issues if you are not familiar with doing this, or make a typo. You might end up needing to reflash. Thanks to @arubislander and @moem for mentioning this.
