hdavid0510 / docker-ubuntu-lxde-novnc

Customized noVNC LXDE ubuntu desktop docker on top of https://github.com/fcwu/docker-ubuntu-vnc-desktop
https://registry.hub.docker.com/r/hdavid0510/ubuntu-desktop-lxde-vnc
9 stars 20 forks source link

failed to register layer: Error processing tar file(exit status 1): write /usr/lib/firefox/libxul.so: no space left on device #9

Closed natea closed 4 years ago

natea commented 4 years ago

When I try to build the image, it stops with this error message:

$ docker build -t hdavid0510/docker-ubuntu-lxde-novnc .
Sending build context to Docker daemon  167.9kB
Step 1/13 : FROM dorowu/ubuntu-desktop-lxde-vnc:bionic
bionic: Pulling from dorowu/ubuntu-desktop-lxde-vnc
35c102085707: Pull complete
251f5509d51d: Pull complete
8e829fe70a46: Pull complete
6001e1789921: Pull complete
7432864fac0c: Pull complete
4de992ab98a9: Pull complete
08271215cfa0: Extracting [==================================================>]  172.6MB/172.6MB
f1fb1dbd1380: Download complete
ed3809743259: Download complete
9e198b6540f4: Download complete
2cd6eb7f26fb: Download complete
fa5ba08ad841: Download complete
14e9aa8f19d9: Download complete
eb94f3a4681c: Download complete
d07e2292d3d0: Download complete
a7945a9bb24c: Download complete
failed to register layer: Error processing tar file(exit status 1): write /usr/lib/firefox/libxul.so: no space left on device
hdavid0510 commented 4 years ago

The last line of the error log, failed to register layer: Error processing tar file(exit status 1): write /usr/lib/firefox/libxul.so: no space left on device might be the problem. Can you check how much space is left on your building environment?

natea commented 4 years ago

yeah, i thought that tool. but my Mac has plenty of free disk space (1TB), so I think the "no space left on device" is happening within the Docker container's volume. Notice it's happening at /usr/lib/firefox which is a directory that i don't even have on my Mac.

On Fri, Jun 5, 2020 at 12:57 AM David.Hong notifications@github.com wrote:

The last line of the error log, failed to register layer: Error processing tar file(exit status 1): write /usr/lib/firefox/libxul.so: no space left on device might be the problem. Can you check how much space is left on your building environment?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hdavid0510/docker-ubuntu-lxde-novnc/issues/9#issuecomment-639258685, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA5BSCAPE5YZZGFU4NBLUDRVB3K7ANCNFSM4NSQ7ZRA .

--

Website: http://www.appsembler.com Blog: http://www.appsembler.com/blog Twitter: http://twitter.com/natea LinkedIn: http://linkedin.com/in/natea Phone: +1 (617) 702-4331

hdavid0510 commented 4 years ago

yeah, i thought that tool. but my Mac has plenty of free disk space (1TB), so I think the "no space left on device" is happening within the Docker container's volume. Notice it's happening at /usr/lib/firefox which is a directory that i don't even have on my Mac.

I did local build successfully without any problem on my environment just a while ago from Dockerfile in this repository, Ubuntu 18.04 with Docker version 19.03.11, build 42e35e61f3. It seems there's something wrong with your environment settings. Did you check where the docker build is actually done? Is that located in a partition with abundant space? For you information, the final image built was 2.81GB big. Much more spare space may required for the partition where you're building this image, as the base image(dorowu/ubuntu-desktop-lxde-vnc:bionic) also is a quite big image(approx. 500MB).

natea commented 4 years ago

These are the disk volumes on my Mac. Anything look it might be a problem in building the Docker image? What's strange is that my Mac's main HD is reporting 1.49TB free disk space.

$ df
Filesystem    512-blocks       Used  Available Capacity     iused               ifree %iused  Mounted on
/dev/disk1s1  3907543608 1043252176 2837454072    27%     2911821 9223372036851863986    0%   /
devfs                460        460          0   100%         796                   0  100%   /dev
/dev/disk1s4  3907543608   25165960 2837454072     1%          14 9223372036854775793    0%   /private/var/vm
map -hosts             0          0          0   100%           0                   0  100%   /net
map auto_home          0          0          0   100%           0                   0  100%   /home
drivefs        272629760  114233352  158396408    42% 18446744069414610847          4294967295 69542124969519000%   /Volumes/GoogleDrive
hdavid0510 commented 4 years ago
$ df
Filesystem    512-blocks       Used  Available Capacity     iused               ifree %iused  Mounted on
/dev/disk1s1  3907543608 1043252176 2837454072    27%     2911821 9223372036851863986    0%   /
devfs                460        460          0   100%         796                   0  100%   /dev
/dev/disk1s4  3907543608   25165960 2837454072     1%          14 9223372036854775793    0%   /private/var/vm
map -hosts             0          0          0   100%           0                   0  100%   /net
map auto_home          0          0          0   100%           0                   0  100%   /home
drivefs        272629760  114233352  158396408    42% 18446744069414610847          4294967295 69542124969519000%   /Volumes/GoogleDrive

The result of df seems to be quite wrong. I'm not a macOS user so I can't tell what's actually going on there with %ifree and %iused on your Mac... I guess the origin of problem you're suffering should be the Docker on Mac, neither Dockerfile nor docker image, as I double checked with different device that there's nothing problematic on Dockerfile that keeps you from building image.

+Edit: Typo fixed.

natea commented 4 years ago

it looks like the Docker volume was maxed out, so i'm resizing it.

On Wed, Jun 10, 2020 at 1:55 AM David.Hong notifications@github.com wrote:

$ df Filesystem 512-blocks Used Available Capacity iused ifree %iused Mounted on /dev/disk1s1 3907543608 1043252176 2837454072 27% 2911821 9223372036851863986 0% / devfs 460 460 0 100% 796 0 100% /dev /dev/disk1s4 3907543608 25165960 2837454072 1% 14 9223372036854775793 0% /private/var/vm map -hosts 0 0 0 100% 0 0 100% /net map auto_home 0 0 0 100% 0 0 100% /home drivefs 272629760 114233352 158396408 42% 18446744069414610847 4294967295 69542124969519000% /Volumes/GoogleDrive

The result of df seems to be quite wrong. I'm not a macOS user so I can't tell what's actually going on there with %ifree and %iused on your Mac... I guess the origin of problem you're suffering should be the Docker on Mac, neither Dockerfile nor docker image, as I double checked with differenct device that there's nothing problematic on Dockerfile that keeps you from building image.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

--

Website: http://www.appsembler.com Blog: http://www.appsembler.com/blog Twitter: http://twitter.com/natea LinkedIn: http://linkedin.com/in/natea Phone: +1 (617) 702-4331

hdavid0510 commented 4 years ago

Please let me know if volume resizing resolved your problem. :)

natea commented 4 years ago

yes, it did! thank you :)

On Mon, Jun 15, 2020 at 10:47 PM David.Hong notifications@github.com wrote:

Please let me know if volume resizing resolved your problem. :)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hdavid0510/docker-ubuntu-lxde-novnc/issues/9#issuecomment-644498503, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA5BSHGQKYYUU3254CF7E3RW3MNJANCNFSM4NSQ7ZRA .

--

Website: http://www.appsembler.com Blog: http://www.appsembler.com/blog Twitter: http://twitter.com/natea LinkedIn: http://linkedin.com/in/natea Phone: +1 (617) 702-4331

hdavid0510 commented 4 years ago

You're welcome. Glad it worked! ╰(°▽°)╯