Closed arthurlutz closed 9 years ago
Hello @arthurlutz,
Thank you for reporting. Could you give us more details about the distribution and the hardware on which you install Cozy?
# cat /etc/debian_version
7.8
# uname -a
Linux host 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt2-1~bpo70+1 (2014-12-08) x86_64 GNU/Linux
is this enough ?
Everything looks good. Can you try to install it again?
This is in a Docker build, I can try again, but I have doubts it will give a different result (ok 3rd time the same). The Docker image base is my own built-from-scratch ubuntu:14.04 (see https://wiki.debian.org/Cloud/CreateDockerImage) so this might be the reason why the result is not the same as with the "official" ubuntu:14.04 (binary blob) image.
I don't know @Kloadut who maintains this repository is not working until next week. It's hard for me to understand what's wrong because other users didn't look to face this problem.
I will give a try to build the image tomorrow or on Friday.
Same thing for me
Sorry I didn't find time to look at the problem.
Hello @arthurlutz can you give us how you build the ubuntu image?
Thanks.
@nledez as mentionned in the comment above : I'm using the mkimage.sh recommended by debian see https://github.com/docker/docker/blob/master/contrib/mkimage.sh , it uses debootstrap.
It may be related to the fact that ImageMagick is missing on your manually built image.
I will take a look
@Kloadut any CMD command that I can add to try out this theory ?
I just saw that imagemagick is installed here https://github.com/cozy-labs/cozy-docker/blob/master/Dockerfile#L14
But I just pushed a new version of the Dockerfile that reset security tokens at container's launching. Maybe you can try out again.
I will try to build an Ubuntu container your way to test.
@arthurlutz I just tested with a manually boostraped ubuntu contrainer, made out of this command:
./mkimage.sh -t kload/ubuntu debootstrap --include=ubuntu-minimal --components=main,universe trusty
And everything went well :)
Hey @Kloadut thanks for taking a look at this. I rebuild my base images with the same options as you and it worked. It seems there is something wrong with my previously built image (I think universe was missing but I added it as a source at the top of the Dockerfile...).
Sorry to wake up an old thread, but I stumble upon the same issue (same ENOENT error at the same stage of building the Docker image), but with different premice.
I've cloned locally the repository and changed in the Dockerfile the base image to be ubuntu:16.04
and replaced trusty
by xenial
line 6.
Restoring back ubuntu:14.04 solve the problem.
I guess this could be related to this issue on Cozy https://github.com/cozy/cozy-debian/issues/37 which state that Ubuntu 16.04 is on the roadmap but not yet supported.