Docker installation not working

Installation
1

I tried launcher rebuild or launcher cleanup, but it keeps bringing up this error. pls help.

 root@vps320093:/var/discourse# ./launcher rebuild app

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

Unable to find image 'discourse/discourse:1.3.7' locally
1.3.7: Pulling from discourse/discourse
7f3a89592205: Pulling fs layer
ec4a109d9ed7: Pulling fs layer
ec4a109d9ed7: Verifying Checksum
ec4a109d9ed7: Download complete
/usr/bin/docker: write /var/lib/docker/tmp/GetImageBlob910720681: no space left on device.
See '/usr/bin/docker run --help'.
Your Docker installation is not working correctly

See: https://meta.discourse.org/t/docker-error-on-bootstrap/13657/18?u=sam
2

You ran out of space in your disk.

3 Likes
3

i just installed discourse recently and i don’t have a lot of posts on my site yet, i don’t think the space should run out like that.
What else could be the problem?

4

Run this command:

df - h
1 Like
5 
Filesystem      Size  Used Avail Use% Mounted on
udev            958M     0  958M   0% /dev
tmpfs           196M  5.7M  190M   3% /run
/dev/vda1       9.7G  9.1G  547M  95% /
tmpfs           977M  916K  976M   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           977M     0  977M   0% /sys/fs/cgroup
tmpfs           100K     0  100K   0% /run/lxcfs/controllers
none            9.7G  9.1G  547M  95% /var/lib/docker/aufs/mnt/6d8b5a72406c3a72827524ef421788bcdd6eb52b8e9ca51ff7fcc632c555dd20
shm              64M  4.0K   64M   1% /var/lib/docker/containers/01555a25e0020b0cd4ac9d6d65148364b56a90f22acdb961c56b8a85eff33e58/shm
tmpfs           196M     0  196M   0% /run/user/0
6

You have a small (10GB) disk only.

There are probably a lot of old docker images around. Try:

./launcher cleanup
2 Likes
7

the output is the same as ./launcher rebuild app
root@vps320093:/var/discourse# ./launcher cleanup

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

Unable to find image 'discourse/discourse:1.3.7' locally
1.3.7: Pulling from discourse/discourse
7f3a89592205: Pulling fs layer
ec4a109d9ed7: Pulling fs layer
/usr/bin/docker: write /var/lib/docker/tmp/GetImageBlob827452230: no space left on device.
See '/usr/bin/docker run --help'.
Your Docker installation is not working correctly
8

You need to free up disk space, your disk is so full that nothing is working.

9

You don’t have space enough to install the space creator :smile:.

  1. Make sure you have a backup saved.

  2. Try this:

docker rm $(docker ps -a -q)
docker rmi $(docker images -q)

Make sure to have a local backup in case this destroys everything!

3 Likes
10

i have done that. it didn’t work.

    root@vps320093:~# docker rm $(docker ps -a -q)
    Error response from daemon: You cannot remove a running container   01555a25e0020b0cd4ac9d6d65148364b56a90f22acdb961c56b8a85eff33e58. Stop the container before attempting removal or use -f

and

root@vps320093:~# docker rmi $(docker images -q)
Untagged: ubuntu:latest
Untagged: ubuntu@sha256:2d44ae143feeb36f4c898d32ed2ab2dffeb3a573d2d8928646dfc9cb7deb1315
Deleted: sha256:f753707788c5c100f194ce0a73058faae1a457774efcda6c1469544a114f8644
Deleted: sha256:3b25e17d01de5200842cadbdc53f4afa1a3ed17a7121e4036e744a83a2732f76
Deleted: sha256:cebd67936ff89b117f72c410b11cc835c96cc8eabd161564ca38bfff99d781f5
Deleted: sha256:5d232b0ea43a530cd4db4be2c175b9dd46f534fa9cc8dcbf1d413c851f74e817
Deleted: sha256:dafccc932aece6c4914ca049df6539b75145ee2cf51f76e8d129aade450c87c3
Deleted: sha256:c854e44a1a5a22c9344c90f68ef6e07fd479e8ce1030fe141e3236887f1a4920
Untagged: samsaffron/docker-gc:latest
Untagged: samsaffron/docker-gc@sha256:1efd5febba28f881c815c37005b09c67fce0fa62d583b82790b0a0fe82cad999
Deleted: sha256:54ca424ca8d6df79c3a82aec01d7aefbf1a9dc7d91986083c74c6100eb703490
Deleted: sha256:43d02a32400acd5615ec64d0fed870241fe4d3b6de989d082f9308db3d13a73d
Deleted: sha256:fdefcee7e2a7f37b340ebb7a7425b87804f8c769da43fd30e27986c89ca732a9
Deleted: sha256:d3e0f5b86a3ac4344a5f60c6b2e16dd65813ee13002cbcd297614fbf5c5d0013
Deleted: sha256:d2b65ed60001d5588e6988227fe8315c74501951744ba98262d98e480d335e02
Deleted: sha256:4f51d825399959586bac782804563b2b4169c6188556bd1eff4aaf630041c17d
Deleted: sha256:15eb0f73cd145d3b46ee4194a68744fe95c82ffcca04b0c8bf38a2678a1d3273
Error response from daemon: conflict: unable to delete 7b53fa7b8414 (cannot be forced) - image is being used by running container 01555a25e002
Error response from daemon: conflict: unable to delete a20f0826357b (cannot be forced) - image has dependent child images
11

what do you think i can delete? cause i have no idea what to delete.

12

That’s your cue :smile:.

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
1 Like
13

I think that was successful.

root@vps320093:~# docker stop $(docker ps -a -q)
01555a25e002
root@vps320093:~# docker rm $(docker ps -a -q)
01555a25e002
root@vps320093:~# docker rmi $(docker images -q)
Untagged: local_discourse/app:latest
Deleted: sha256:7b53fa7b841498701db14b96fd243d6f2021b2d5309d35689775d37d7901debc
Deleted: sha256:c791db6644416e096b660cd52921fa54f4f448a50875972672350e4b2ad2764d
Untagged: discourse/discourse:1.3.5
Untagged: discourse/discourse@sha256:a3fffe0bc4a462c52429e4986932a1733be384f9211e7e48f14864bd9306fb53
Deleted: sha256:a20f0826357b766fd4836e93abbb3a9a406cfcb8fe33e5217efbd9de1ffb42c4
Deleted: sha256:f8b65395a6b85643abdab9dac85a74e33f27bc40f18e7ff911e214de80c2217b
Deleted: sha256:5c1855b633cf4164ea803930239931c05f919508c12ef6f6867d64130abd6072
Deleted: sha256:a77ab7a1e96c04bddc85e630f45989915c026c554e2bf35425932d7148445bd4
Deleted: sha256:e78a860262f22262d951578359f15931d121f6b5c9eee52f23103a9f0087fc5d
Deleted: sha256:fcc35457d7fbd6cfa775ee8bcb73a84f807e46e24c07971fbbd05ddacd07b70d
Deleted: sha256:1ed5e1541452b1263995eb60a26ec9c9d54f7308deee09f5762dbf383284c5e8
Deleted: sha256:aef58136e84abefb8c091da8e51129776ddfb885b43fdb04ed1f746ca1477b48
Deleted: sha256:7aae4540b42d10456f8fdc316317b7e0cf3194ba743d69f82e1e8b10198be63c

my site is currently down at the moment.
so, what will i do next ?

14 
./launcher start app
2 Likes
15

Actually rebuild, all images are nuked

4 Likes
16

its working perfectly now. and i have available 1.5GB. I think i will have to get an additional disk.
Thank You so much for your help. You guys are the best. :grinning:

root@vps320093:/var/discourse# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            958M     0  958M   0% /dev
tmpfs           196M  8.1M  188M   5% /run
/dev/vda1       9.7G  8.3G  1.5G  86% /
tmpfs           977M  464K  976M   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           977M     0  977M   0% /sys/fs/cgroup
tmpfs           100K     0  100K   0% /run/lxcfs/controllers
tmpfs           196M     0  196M   0% /run/user/0
none            9.7G  8.3G  1.5G  86% /var/lib/docker/aufs/mnt/0fd6737df6289e4512fb214ad4d1ba252751688c5138ebdcef53ab71c0a30911
shm              64M  4.0K   64M   1% /var/lib/docker/containers/9230cf44b75ed80400ec854cf396ef437c03869211a9013e4c5e843381038709/shm
4 Likes
17

Hey, that looks like OVH’s VPS SSD, the cheapest option, right? In terms of CPU performance those are nifty little servers, but the 10GB storage will not take you far.

If you do not have a lot of concurrent users and your budget is a dime, then ScaleWay’s VPS is a perfectly usable option. It comes with 2 slow CPU cores, 2GB RAM and a nice 50GB storage. The staff here complains that they are slow, but in real life it runs OK (depending on traffic, of course).

I asked the additional volumes question here earlier, but did not a get a reply. That remains as an interesting question, even though I now have a beefy 200GB SSD on my new box.

1 Like
18

This topic was automatically closed after 24 hours. New replies are no longer allowed.