search

mhubig / docker-partkeepr

mhubig/partkeepr docker image repository
62 stars 64 forks source link

Creating partkeepr on synology nas #11

Closed Jonas-Meyer97 closed 6 years ago

Jonas-Meyer97 commented 6 years ago

Hi, i tried to use this docker on my synology nas. At first i tried to install it with the synology docker gui but it just keeped up restarting the docker. After that i tried to run the docker via ssh. Below are the things i entered. After i got a permission error with port 80 i changed the port to 8011 i think synology already uses port 80.

wget https://github.com/mhubig/docker-partkeepr/archive/1.4.0-1.tar.gz
tar -xvf 1.4.0-1.tar.gz
rm 1.4.0-1.tar.gz
mv docker-partkeepr-1.4.0-1/ partkeepr
cd partkeepr/
sudo docker pull mhubig/partkeepr
EDIT docker-compose.yml - "80:80" => - "8011:80"
EDIT apache.conf <VirtualHost *:80> => <VirtualHost *:8011>
docker-compose --verbose up |& tee `docker-compose-log.txt
docker export partkeepr_partkeepr_1 > partkeepr.tar

Here are the docker log files from the synology gui. 

partkeepr_partkeepr_1       
date        stream  content
8/17/2018   21:12   stderr  [Fri Aug 17 21:12:54.958067 2018] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

8/17/2018   21:12   stderr  [Fri Aug 17 21:12:54.957902 2018] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.25 (Debian) PHP/7.1.18 configured -- resuming normal operations

8/17/2018   21:12   stderr  "AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message"
8/17/2018   21:12   stderr  "AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message"
partkeepr_database_1        
date        stream  content
8/17/2018   21:12   stderr  Version: '10.3.9-MariaDB-1:10.3.9+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] mysqld: ready for connections.

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] Added new Master_info '' to hash table

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] Reading of all Master_info entries succeded

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Warning] 'proxies_priv' entry '@% root@255a1aa0a1f9' ignored in --skip-name-resolve mode.

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] Server socket created on IP: '::'.

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: Buffer pool(s) load completed at 180817 21:12:51

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] Plugin 'FEEDBACK' is disabled.

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: 10.3.9 started; log sequence number 1631066; transaction id 21

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: Waiting for purge to start

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: Creating shared tablespace for temporary tables

8/17/2018   21:12   stderr  2018-08-17 21:12:51 0 [Note] InnoDB: 128 out of 128 rollback segments are active.

8/17/2018   21:12   stderr  "2018-08-17 21:12:50 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
"   
8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Completed initialization of buffer pool

8/17/2018   21:12   stderr  "2018-08-17 21:12:50 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
"   
8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Using SSE2 crc32 instructions

8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Number of pools: 1

8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Uses event mutexes

8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] InnoDB: Using Linux native AIO

8/17/2018   21:12   stderr  2018-08-17 21:12:50 0 [Note] mysqld (mysqld 10.3.9-MariaDB-1:10.3.9+maria~bionic) starting as process 1 ...

Looking at the docker-compose-log.txt it seems it hangs at the docker-php-entrypoint / docker-entrypoint.sh part at least that the point where i pressed CTRL+C because nothing else was happening.

compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'fc6f69d895e2b3527677370c33916412beb1615d990dad3ec38ecd9cba9b084a')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'docker-default',
 u'Args': [u'apache2-foreground'],
 u'Config': {u'ArgsEscaped': True,
             u'AttachStderr': False,
             u'AttachStdin': False,
             u'AttachStdout': False,
             u'Cmd': [u'apache2-foreground'],
             u'DDSM': False,
             u'Domainname': u'',
             u'Entrypoint': [u'docker-php-entrypoint'],
...
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'aa9119147d3ec309457d9e0bb1c52b2111ed9c69d6805d3e0f7a883dba217532')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'docker-default',
 u'Args': [u'mysqld'],
 u'Config': {u'ArgsEscaped': True,
             u'AttachStderr': False,
             u'AttachStdin': False,
             u'AttachStdout': False,
             u'Cmd': [u'mysqld'],
             u'DDSM': False,
             u'Domainname': u'',
             u'Entrypoint': [u'docker-entrypoint.sh'],

Keep in mind im not really a Linux user or very familiar with docker apart from copy pasting commands to install them so here are a few guesses of mine about what might be the problem:

  1. If i execute ls in the partkeepr/ folder where i run docker-compose there is not even a docker-entrypoint.sh so docker didn't even get so far or there was a file permission problem or it just hidden from me in docker itself?
  2. There is a file permission error wher i should mount a folder to my synology store

Hope someone can help me with this.

docker-compose-log.txt

Google Drive: Archive of the docker container: partkeepr.tar

mhubig commented 6 years ago

The only thing you need to change, if port 80 on your synology is already taken, is the port within docker-compose.yml. Changing it to 8011:80 as you already did is korrekt! Now starting the system with docker-compose up you should be able to connect to partkeepr at http://ip-of-synology-nas:8011/setup. If this is not possible you may need to open port 8011 within the security / firewall setting of your NAS.

Jonas-Meyer97 commented 6 years ago

Thanks. Everything is working fine now.