Repository navigation
Install Qnap ARM problem #5
Description
I'm runing docker inside Qnap AL212 Dual-core ARM Cortex-A15 CPU @ 1.70GHz (TS-431P)
docker -v
Docker version 17.09.1-ce, build 0bbe3ac
I have three problemas:
1.- postfix not run
dirvish_1 | ls: cannot access '/var/spool/postfix/maildrop': Operation not permitted
dirvish_1 | ls: cannot access '/var/spool/postfix/pid': Operation not permitted
dirvish_1 | ls: cannot access '/var/spool/postfix/private': Operation not permitted
dirvish_1 | ls: cannot access '/var/spool/postfix/public': Operation not permitted
dirvish_1 | ls: cannot access '/var/spool/postfix/saved': Operation not permitted
dirvish_1 | ls: cannot access '/var/spool/postfix/trace': Operation not permitted
dirvish_1 | ls: cannot access '/var/spool/postfix/usr': Operation not permitted
dirvish_1 | Sep 19 06:23:52 localhost postfix/postfix-script[2473]: warning: not owned by postfix: .
dirvish_1 | Sep 20 01:44:24 localhost postfix/postfix-script[2474]: warning: not owned by postfix: ./dev
dirvish_1 | Sep 14 08:04:08 localhost postfix/postfix-script[2475]: warning: not owned by postfix: ./etc
dirvish_1 | Sep 17 06:36:40 localhost postfix/postfix-script[2476]: warning: not owned by postfix: ./etc/services
dirvish_1 | Sep 19 20:03:04 localhost postfix/postfix-script[2477]: warning: not owned by postfix: ./etc/reso
2.- Terminal inside docker
date
Thu Jan 1 01:00:00 CET 1970
3.- list directory
ls -l
ls: cannot access 'bin': Operation not permitted
ls: cannot access 'boot': Operation not permitted
ls: cannot access 'dev': Operation not permitted
.
d????????? ? ? ? ? ? backups
d????????? ? ? ? ? ? bin
d????????? ? ? ? ? ? boot
d????????? ? ? ? ? ? config
d????????? ? ? ? ? ? container
d????????? ? ? ? ? ? dev
d????????? ? ? ? ? ? etc
d????????? ? ? ? ? ? home
Can you help me?
Activity
MarvAmBass commentedon Oct 7, 2022
interessting, this shouldn't make problems.
It might be that qnap has some security settings, that it overwrites the default user with some random uid user and tries to start the container
I guess my container needs root permissions to start all the needed services
maybe you can check that and try to start it with more/normal permissions