dive fails in main.go

[k3ck3c]

dive fails in main.go

[wagoodman]

I can give that a shot, what version of dive did you use?

[k3ck3c]

dive 0.0.8

I guess it is the latest (pip installed yesterday)

[k3ck3c]

I noticed a 24 GB file was created in /tmp

$ ll /tmp/dive*
/tmp/dive267197208:
total 44
drwx------ 2 gg gg 4096 nov. 4 16:06 .
drwxrwxrwt 27 root root 36864 nov. 4 16:23 ..

/tmp/dive055914020:
total 24730792
drwx------ 2 gg gg 4096 nov. 4 16:15 .
-rw-r--r-- 1 gg gg 25324040192 nov. 4 16:19 image.tar
drwxrwxrwt 27 root root 36864 nov. 4 16:23 ..
$

I have some more free space

$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 3,9G 0 3,9G 0% /dev
tmpfs 789M 32M 758M 4% /run
/dev/sda5 190G 151G 30G 84% /
tmpfs 3,9G 205M 3,7G 6% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/loop2 88M 88M 0 100% /snap/core/5548
/dev/loop1 145M 145M 0 100% /snap/notepadqq/855
/dev/loop4 145M 145M 0 100% /snap/notepadqq/841
/dev/loop3 88M 88M 0 100% /snap/core/5662
/dev/sda1 256M 30M 227M 12% /boot/efi
tmpfs 789M 160K 788M 1% /run/user/1000
/dev/loop5 88M 88M 0 100% /snap/core/5742
$

[k3ck3c]

well on another computer running Debian 9 instead if Ubuntu, it works fine, so I guess something is wrong on my Ubuntu computer

[wagoodman]

@k3ck3c I haven't been able to reproduce this, however the left over temp dir on crash is bad! I've fixed that issue and it should make it in the v0.3.0 release. I'll close this for now, though if you run into this problem again feel free to open another issue and add any additional info.

[k3ck3c]

thanks for your time! I guess I will not use much this version 2.7.8 of Captvty as the author recommends moving to the V3, which worked fine with dive. Le dim. 25 nov. 2018 à 03:04, Alex Goodman <[email protected]> a écrit :

…

@k3ck3c <https://github.com/k3ck3c> I haven't been able to reproduce this, however the left over temp dir on crash is bad! I've fixed that issue and it should make it in the v0.3.0 release. I'll close this for now, though if you run into this problem again feel free to open another issue and add any additional info. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#58 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC-z09TPzt2TyS_xaA_G7IFdYrUUO9l-ks5uyfrLgaJpZM4YMYKa> .