can't install git dependencies

0

Hi!

I'm getting the following error message when I log into EC2:

Failed to install dependencies for "Git" panel We can’t install required dependencies because of how your AWS Cloud9 environment is currently configured. Error: No space left on device. Please make sure you have at least 200MB of free disk space.

I've looked through the forum and I don't see any similar questions unfortunately.

I looked at my disk with df -h and got:

df -h

Filesystem Size Used Avail Use% Mounted on udev 2.0G 0 2.0G 0% /dev tmpfs 395M 916K 394M 1% /run /dev/vda1 25G 20G 4.2G 83% / tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/loop0 106M 106M 0 100% /snap/core/16091 /dev/loop1 106M 106M 0 100% /snap/core/16202 /dev/vda15 105M 8.9M 96M 9% /boot/efi tmpfs 395M 0 395M 0% /run/user/0

I'm unsure of what the issue is - only loop0 and loop1 are full and I'm assuming this OK as they seem to be sized to exactly what is required...

Any ideas as I'm stuck here...?

Thank you!

Mark

asked 4 months ago223 views
4 Answers
1

Hello,

  • Delete any unnecessary or large files on the instance to free up space on the root filesystem. Make sure to check folders like /var/log for log files that could be cleared out.
  • You can also check the Cloud9 logs or the system logs in /var/log for any errors related to lack of disk space during the installation process. Hopefully clearing some space will do the trick
  • As a last resort, you may need to resize the root volume to provide more space. This would require stopping the instance first.
  • In some cases, you might need to adjust the disk quota for snap packages.

Thanks

Abhinav

answered 4 months ago
1

You can modify the quota by editing the /etc/systemd/system/snapd.service file and adding the --max option to the ExecStart line. For example:

ExecStart=/usr/lib/snapd/snapd --max=400MB

After modifying the file, restart the snap service using sudo systemctl restart snapd.service

But I would suggest to first try to focus on other issues mentioned in my earlier response

Thanks,

Abhinav

answered 4 months ago
0

Hi,

Thanks for the answer. This could be applicable:

In some cases, you might need to adjust the disk quota for snap packages.

The snap dirs do show 100%, is this OK? If not, how would I adjust the quota for them?

Thanks,

Mark

answered 4 months ago
0

Hi!

OK, thanks! I tried the other items that you suggested already:

  1. removed some large files from /var/logs
  2. checked logs for errors
  3. root has enough space
root@pdfservice:/etc/systemd/system# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           395M  916K  394M   1% /run
/dev/vda1        25G   20G  4.2G  83% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/loop0      106M  106M     0 100% /snap/core/16091
/dev/loop1      106M  106M     0 100% /snap/core/16202
/dev/vda15      105M  8.9M   96M   9% /boot/efi
tmpfs           395M     0  395M   0% /run/user/0

So I went to where you recommended but no snapd.service file:

df -h
drwxr-xr-x 17 root root 4096 Oct  5 11:00 .
drwxr-xr-x  5 root root 4096 Sep 14  2022 ..
drwxr-xr-x  2 root root 4096 Jun 17  2019 cloud-final.service.wants
drwxr-xr-x  2 root root 4096 Jul  1  2022 cloud-init.target.wants
lrwxrwxrwx  1 root root   42 Mar  4  2020 dbus-fi.w1.wpa_supplicant1.service -> /lib/systemd/system/wpa_supplicant.service
lrwxrwxrwx  1 root root   40 Mar  4  2020 dbus-org.freedesktop.ModemManager1.service -> /lib/systemd/system/ModemManager.service
lrwxrwxrwx  1 root root   53 Mar  4  2020 dbus-org.freedesktop.nm-dispatcher.service -> /lib/systemd/system/NetworkManager-dispatcher.service
lrwxrwxrwx  1 root root   44 Jun 17  2019 dbus-org.freedesktop.resolve1.service -> /lib/systemd/system/systemd-resolved.service
drwxr-xr-x  2 root root 4096 Mar 21  2023 default.target.wants
-rw-r--r--  1 root root  371 Jul 23  2019 do-agent.service
-rw-r--r--  1 root root  363 Jul 30  2019 do-agent.service.dpkg-dist
-rw-r--r--  1 root root  358 Jun 24  2022 droplet-agent.service
drwxr-xr-x  2 root root 4096 Jun 17  2019 final.target.wants
drwxr-xr-x  2 root root 4096 Jun 17  2019 getty.target.wants
drwxr-xr-x  2 root root 4096 Jun 17  2019 graphical.target.wants
lrwxrwxrwx  1 root root   38 Jun 17  2019 iscsi.service -> /lib/systemd/system/open-iscsi.service
drwxr-xr-x  2 root root 4096 Oct  5 11:00 multi-user.target.wants
drwxr-xr-x  2 root root 4096 Mar  4  2020 network-online.target.wants
drwxr-xr-x  2 root root 4096 Jun 17  2019 open-vm-tools.service.requires
drwxr-xr-x  2 root root 4096 Jun 17  2019 paths.target.wants
-rw-r--r--  1 root root  346 Sep 19 03:38 snap-core-16091.mount
-rw-r--r--  1 root root  346 Oct  5 10:59 snap-core-16202.mount
drwxr-xr-x  2 root root 4096 Oct  5 11:00 snapd.mounts.target.wants
drwxr-xr-x  2 root root 4096 Jun 17  2019 sockets.target.wants
drwxr-xr-x  2 root root 4096 Jul  1  2022 sshd-keygen@.service.d
lrwxrwxrwx  1 root root   31 Jun 17  2019 sshd.service -> /lib/systemd/system/ssh.service
drwxr-xr-x  2 root root 4096 Jun 17  2019 sysinit.target.wants
lrwxrwxrwx  1 root root   35 Jun 17  2019 syslog.service -> /lib/systemd/system/rsyslog.service
drwxr-xr-x  2 root root 4096 Jun 17  2019 timers.target.wants
lrwxrwxrwx  1 root root   41 Aug 25  2022 vmtoolsd.service -> /lib/systemd/system/open-vm-tools.service

Any other ideas?

Thank you very much!

Mark

answered 4 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions