Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloud not start with Volume Mapping #18

Open
mac-linux-free opened this issue Aug 9, 2020 · 6 comments
Open

Cloud not start with Volume Mapping #18

mac-linux-free opened this issue Aug 9, 2020 · 6 comments

Comments

@mac-linux-free
Copy link

Hello,

I could not start the container with volume mapping. If I leave out "-v /var/piler-data...." it is working.

What am I doing wrong?

Thank you.

@woa7
Copy link
Owner

woa7 commented Aug 20, 2020

@mac-linux-free can you please post the full docker command

@mac-linux-free
Copy link
Author

docker run -d --name piler -p 25:25 -p 80:80 -p 443:443 -v /root/piler-data:/var/piler -e PILER_HOST=archive.tld.de woa7/piler

@mac-linux-free
Copy link
Author

if I start the container without the volume mapping and stop it and rsync the /var/lib/docker/volumes/... to /root/piler-data the volume mapping is working

@woa7
Copy link
Owner

woa7 commented Aug 21, 2020

its sounds like a ID problem.
can you please start it with the right IDs?
like with
-e PUID=$(id -u) -e PGID=$(id -g)

more info is also in the readme https://github.com/woa7/docker-piler/blob/master/README.md

@q20
Copy link

q20 commented Apr 26, 2021

On a Synology I have a similar issue. Though started with:

sudo docker create \ --name=piler \ -e PUID=$(id -u) \ -e PGID=$(id -g) \

I see the following:

date stream content
2021-04-26 14:59:35 stdout [s6-finish] sending all processes the KILL signal and exiting.
2021-04-26 14:59:32 stdout [s6-finish] sending all processes the TERM signal.
2021-04-26 14:59:32 stdout [s6-finish] waiting for services.
2021-04-26 14:59:32 stdout [cont-finish.d] done.
2021-04-26 14:59:32 stdout [cont-finish.d] executing container finish scripts...
2021-04-26 14:59:32 stdout [cmd] /bin/bash exited 1
2021-04-26 14:59:32 stdout FATAL: failed to open /var/piler/sphinx/main1.spl: No such file or directory, will not index. Try --rotate option.
2021-04-26 14:59:32 stdout indexing index 'main1'...
2021-04-26 14:59:32 stdout using config file '/etc/piler/sphinx.conf'...
2021-04-26 14:59:32 stdout  
2021-04-26 14:59:32 stdout Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
2021-04-26 14:59:32 stdout Copyright (c) 2001-2018, Andrew Aksyonoff
2021-04-26 14:59:32 stdout Sphinx 3.1.1 (commit 612d99f)
2021-04-26 14:59:28 stdout Initializing sphinx indices
2021-04-26 14:59:28 stdout Done.
2021-04-26 14:59:28 stdout Writing sphinx configuration
2021-04-26 14:59:28 stdout Done.
2021-04-26 14:56:26 stdout Creating mysql database
2021-04-26 14:56:26 stdout ...done.
2021-04-26 14:56:21 stdout * Starting MariaDB database server mysqld
2021-04-26 14:56:20 stdout ...done.
2021-04-26 14:56:20 stderr rsyslogd: activation of module imklog failed [v8.32.0 try http://www.rsyslog.com/e/2145 ]
2021-04-26 14:56:20 stderr rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
2021-04-26 14:56:20 stdout * Starting enhanced syslogd rsyslogd
2021-04-26 14:56:19 stdout [services.d] done.
2021-04-26 14:56:19 stdout [services.d] starting services
2021-04-26 14:56:19 stdout [cont-init.d] done.
2021-04-26 14:56:19 stdout [cont-init.d] 99-custom-scripts: exited 0.
2021-04-26 14:56:19 stdout [custom-init] no custom files found exiting...
2021-04-26 14:56:19 stdout [cont-init.d] 99-custom-scripts: executing...
2021-04-26 14:56:19 stdout [cont-init.d] 10-adduser: exited 0.
2021-04-26 14:56:19 stdout  
2021-04-26 14:56:19 stdout -------------------------------------
2021-04-26 14:56:19 stdout User gid:    100
2021-04-26 14:56:19 stdout User uid:    1024
2021-04-26 14:56:19 stdout  
2021-04-26 14:56:19 stdout -------------------------------------
2021-04-26 14:56:19 stdout GID/UID
2021-04-26 14:56:19 stdout -------------------------------------
2021-04-26 14:56:19 stdout https://www.linuxserver.io/donate/
2021-04-26 14:56:19 stdout To support LSIO projects visit:
2021-04-26 14:56:19 stdout  
2021-04-26 14:56:19 stdout -------------------------------------
2021-04-26 14:56:19 stdout Brought to you by linuxserver.io
2021-04-26 14:56:19 stdout  
2021-04-26 14:56:19 stdout  
2021-04-26 14:56:19 stdout || |/ ||  _/
2021-04-26 14:56:19 stdout | | __ \ | | | () |
2021-04-26 14:56:19 stdout | | / __| | |  /  \
2021-04-26 14:56:19 stdout | |  ___   _    __
2021-04-26 14:56:19 stdout _         ()
2021-04-26 14:56:19 stdout -------------------------------------
2021-04-26 14:56:19 stdout  
2021-04-26 14:56:16 stdout [cont-init.d] 10-adduser: executing...
2021-04-26 14:56:16 stdout [cont-init.d] 01-envfile: exited 0.
2021-04-26 14:56:16 stdout [cont-init.d] 01-envfile: executing...
2021-04-26 14:56:16 stdout [cont-init.d] executing container initialization scripts...
2021-04-26 14:56:16 stdout [fix-attrs.d] done.
2021-04-26 14:56:16 stdout [fix-attrs.d] applying ownership & permissions fixes...
2021-04-26 14:56:16 stdout [s6-init] ensuring user provided files have correct perms...exited 0.
2021-04-26 14:56:16 stdout [s6-init] making user provided files available at /var/run/s6/etc...exited 0.

Suggestions? : )

@q20
Copy link

q20 commented May 6, 2021

I managed to resolve this by using Portainer to create NFS volumes for the piler container. Like this:
image

This allowed for easy RW access to the correct directory.

One important discovery I made after this success: when recreating/updating the container, all config info is lost, along with the mySQL database.
I therefore created in total 3x volumes for this container:
image

This has allowed the database and configuration to be preserved across updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants