search

bjuretko / docker-baikal-infcloud

CalDAV/CardDAV Server with dockerized lighthttpd + baikal + sqlite + infcloud bundle
10 stars 5 forks source link

lighttpd.conf failed build #28

Open alfureu opened 5 years ago

alfureu commented 5 years ago

Trying to rebuild this and getting this strange error:

 ---> Using cache
 ---> e4c07d6f4b64
Step 11/18 : COPY lighttpd.conf /etc/lighttpd/lighttpd.conf
ERROR: Service 'baikal' failed to build: COPY failed: stat /volume1/.@plugins/AppCentral/docker-ce/docker_lib/tmp/docker-builder235021056/lighttpd.conf: no such file or directory

It always tries to copy into a different folder, which is based on the docker-compose.yaml read-only, and the file is just not there. I followed all the steps in the tutorial.

bjuretko commented 5 years ago

Not really sure what you are doing, but try to remove the file .dockerignore from the project folder before build. If this does not help, what do I need to do to reproduce?

bjuretko commented 5 years ago

Anyway: why it is building? Did you use the image from this repos' release page?

alfureu commented 5 years ago

I build because I do not have make available on my NAS, and even if I install it through entware, it does not compile. So I use the commands from the Makefile

bjuretko commented 5 years ago

so what's your build command?

alfureu commented 5 years ago 
sudo docker build --build-arg TIMEZONE=Europe/Berlin--tag "alpine-infcloud-baikal:3.9-0.13.1-0.5.2" --tag "alpine-infcloud-baikal:latest" --no-cache .

rm "alpine-infcloud-baikal.3.9-0.13.1-0.5.2.tgz" || true
docker image save --output "alpine-infcloud-baikal.3.9-0.13.1-0.5.2.tgz" "alpine-infcloud-baikal:3.9-0.13.1-0.5.2"

docker run --publish 8800:8800 --volume "/volume1/home/docker/docker-baikal-infcloud/baikal:/var/www/baikal/Specific" alpine-infcloud-baikal
bjuretko commented 5 years ago

There is a missing "space" before --tag in first line TIMEZONE=Europe/Berlin--tag "alpine... so the image is not tagged correctly nor is the build arg correct.

alfureu commented 5 years ago

Thanks @bjuretko that was the issue. Sorry, was completely blind not noticing that problem.

I have one more question: if I use sqlite, and I need to rebuild again, how can I preserve the database? I have a mounted volume of baikal/Specific but in case I will need to rebuild the container again, how can I preserve the database and just re-link it again?

bjuretko commented 5 years ago

the volume should be preserved (at least thats the idea of them, because otherwise you could just store them in the container which will then be lost if you update the container). Anyway ... it is good make a backup of the volume data before this and just check it out with your provider.

see https://docs.docker.com/engine/reference/commandline/volume/