Torizon: Low space?

Hi team,

I’m trying to run our grafana demo, and when running the docker-compose up command, the module runs out of eMMC space.

I could confirm this with the df command: By default, the used space is already at 90% without any container running:

colibri-imx8x-v10b-06410677:~$ df
Filesystem                 1K-blocks    Used Available Use% Mounted on
tmpfs                         898580   25764    872816   3% /run
devtmpfs                      401612       0    401612   0% /dev
/dev/disk/by-label/otaroot   3615352 3037384    374604  90% /sysroot
tmpfs                         898580       0    898580   0% /dev/shm
tmpfs                         898580       0    898580   0% /sys/fs/cgroup
tmpfs                         898580       0    898580   0% /tmp
tmpfs                         898580      12    898568   1% /var/volatile
tmpfs                         179716       0    179716   0% /run/user/1220    

Simply running docker-compose up, it fills up and gives an error during the pull/extract:

colibri-imx8x-v10b-06410677:~/grafana$ docker-compose up
Pulling kiosk (torizon/arm64v8-debian-kiosk-mode-browser:latest)...
latest: Pulling from torizon/arm64v8-debian-kiosk-mode-browser
f7ca645dfd2f: Extracting [==================================================>]  25.85MB/25.85MB
3695c8be206e: Download complete
ec243374cdfe: Download complete
27864f199efa: Download complete
5ac2cc5dc64f: Download complete
052327b3f035: Download complete
f7ca645dfd2f: Pull complete
3695c8be206e: Pull complete
ec243374cdfe: Pull complete
27864f199efa: Pull complete
5ac2cc5dc64f: Pull complete
052327b3f035: Pull complete
0c8310624258: Pull complete
ee74f2eee1bd: Pull complete
70e0b6b50e0f: Pull complete
c43cf5a73ae4: Pull complete
6fc954135a3f: Pull complete
770d1c3b2a51: Pull complete
f4ca30f332a8: Pull complete
c981ffa0ebad: Pull complete
e46d7833e734: Pull complete
a9baa919384a: Pull complete
87c506ef90fe: Pull complete
1fd76b93b594: Extracting [==================================================>]  144.4MB/144.4MB

ERROR: failed to register layer: Error processing tar file(exit status 1): write /usr/lib/chromium/chromium: no space left on device

Am I missing something? I didn’t do any OTA or anything that could consume all that space… Maybe all those unused 800MBs could be better spared somewhere else? Thanks.

Thanks Valter, I had a bunch of old stuff there, good to know about that command :slight_smile: docker system prune helped on reducing this a lot.

colibri-imx8x-v10b-06410677:~$ docker images
REPOSITORY                                                                 TAG                 IMAGE ID            CREATED             SIZE
grafana_collectd                                                           latest              95371a260413        56 minutes ago      105MB
fatorizondemo_ws-service                                                   latest              ab4fbb3b8c30        About an hour ago   119MB
<none>                                                                     <none>              1623a0009034        2 hours ago         119MB
<none>                                                                     <none>              057b038302a6        2 hours ago         119MB
fatorizondemo_temp                                                         latest              94164e93aeff        5 hours ago         115MB
<none>                                                                     <none>              508d85f1b511        5 hours ago         115MB
<none>                                                                     <none>              bc1fb95b784e        5 hours ago         115MB
<none>                                                                     <none>              53dd0fc9b4de        5 hours ago         119MB
<none>                                                                     <none>              39e9bdd9805f        5 hours ago         115MB
<none>                                                                     <none>              f7c97adf3162        5 hours ago         115MB
<none>                                                                     <none>              963064e0df71        5 hours ago         115MB
<none>                                                                     <none>              bbb565cd4bc8        5 hours ago         119MB
alvarotx/fatorizondemo                                                     latest              0fd9d3c99ea4        6 hours ago         278MB
alvarotx/fatorizondemo                                                     <none>              1d82f143f8a4        7 hours ago         278MB
alvarotx/fatorizondemo                                                     <none>              0ac1b45a64bd        7 hours ago         278MB
arm64v8-debian-python3_buster_862af9ad-6a7d-42f5-8580-dbdcc5d3e68c_debug   latest              96d6bcf44d22        7 hours ago         152MB
influxdb                                                                   1.7.10              fe20eb3597b2        2 weeks ago         298MB
torizon/arm64v8-debian-weston-vivante                                      latest              241416ec9af2        2 weeks ago         479MB
torizon/arm32v7-debian-base                                                latest              397355388e5b        2 weeks ago         55.2MB
torizon/arm64v8-debian-base                                                buster              284777040c7f        2 weeks ago         71.6MB
torizon/arm64v8-debian-base                                                latest              284777040c7f        2 weeks ago         71.6MB
torizon/arm64v8-debian-dev-tools                                           latest              0493159c406d        5 weeks ago         210MB
grafana/grafana                                                            6.7.1               3a0cccd9a5aa        3 months ago        128MB
torizonextras/arm64v8-gpiod                                                latest              b2d34bf17cc3        5 months ago        72MB

Can you try to run:

docker images

and post the output?
That would help understanding what is using that space.
You can also recover space by running:

docker system prune