marius311 / boinc-server-docker Goto Github PK

View Code? Open in Web Editor NEW

121.0 121.0 58.0 230 KB

A Docker multi-container application that runs a BOINC server

License: MIT License

Makefile 8.77% Shell 47.13% Dockerfile 44.11%

boinc docker science volunteer-computing

boinc-server-docker's People

Contributors

Stargazers

Watchers

boinc-server-docker's Issues

Boinc client don't see tasks on server

Hi marius, i've small problem. I run boinc server and submit tasks. You can see this in the picture below

But i don't see tasks on client via BOINC Manager or boinccmd, boinccmd tells me that no task on server

I've ubuntu 16.04 with installed VirtualBox and enabled virtualization. BOINC Manager tells that VirtualBox not installed, although i installed her, maybe it's related. Sorry for bad english)

404 Not Found for 127.0.0.1/boincserver

I am trying to setup a BOINC server but I am getting a 404 on http://127.0.0.1/boincserver:

$ wget http://127.0.0.1/boincserver
--2019-01-24 16:18:44--  http://127.0.0.1/boincserver
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-01-24 16:18:44 ERROR 404: Not Found.

However, I do not see anything suspicious when I start with docker-compose (log at the end of this post).

I have tried running docker-compose down -v before running as well. Here are my docker and docker compose versions:

$ docker --version
Docker version 18.09.1, build 4c52b90
$ docker-compose --version
docker-compose version 1.23.2, build 1110ad01

Docker compose up log:

$ docker-compose up
Creating network "boinc-server-docker_default" with the default driver
Creating volume "boinc-server-docker_mysql" with default driver
Creating volume "boinc-server-docker_project" with default driver
Creating volume "boinc-server-docker_results" with default driver
Creating volume "boinc-server-docker_secrets" with default driver
Creating boinc-server-docker_makeproject_1 ... done
Creating boinc-server-docker_mysql_1       ... done
Creating boinc-server-docker_apache_1      ... done
Attaching to boinc-server-docker_makeproject_1, boinc-server-docker_mysql_1, boinc-server-docker_apache_1
makeproject_1  | Updating project files in data volume...
mysql_1        | Initializing database
apache_1       | /usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
apache_1       |   'Supervisord is running as root and it is searching '
apache_1       | 2019-01-24 08:18:03,670 CRIT Supervisor running as root (no user in config file)
apache_1       | 2019-01-24 08:18:03,670 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
apache_1       | 2019-01-24 08:18:03,692 INFO RPC interface 'supervisor' initialized
apache_1       | 2019-01-24 08:18:03,693 CRIT Server 'unix_http_server' running without any HTTP authentication checking
apache_1       | 2019-01-24 08:18:03,696 INFO supervisord started with pid 1
apache_1       | 2019-01-24 08:18:04,699 INFO spawned: 'cron' with pid 8
apache_1       | 2019-01-24 08:18:04,700 INFO spawned: 'start' with pid 9
apache_1       | 2019-01-24 08:18:04,704 INFO spawned: 'rsyslogd' with pid 10
apache_1       | 2019-01-24 08:18:04,711 INFO spawned: 'apache2' with pid 11
apache_1       | 2019-01-24 08:18:04,917 INFO exited: start (exit status 1; not expected)
mysql_1        |
mysql_1        |
mysql_1        | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
mysql_1        | To do so, start the server, then issue the following commands:
mysql_1        |
mysql_1        | '/usr/bin/mysqladmin' -u root password 'new-password'
mysql_1        | '/usr/bin/mysqladmin' -u root -h  password 'new-password'
mysql_1        |
mysql_1        | Alternatively you can run:
mysql_1        | '/usr/bin/mysql_secure_installation'
mysql_1        |
mysql_1        | which will also give you the option of removing the test
mysql_1        | databases and anonymous user created by default.  This is
mysql_1        | strongly recommended for production servers.
mysql_1        |
mysql_1        | See the MariaDB Knowledgebase at http://mariadb.com/kb or the
mysql_1        | MySQL manual for more instructions.
mysql_1        |
mysql_1        | Please report any problems at http://mariadb.org/jira
mysql_1        |
mysql_1        | The latest information about MariaDB is available at http://mariadb.org/.
mysql_1        | You can find additional information about the MySQL part at:
mysql_1        | http://dev.mysql.com
mysql_1        | Consider joining MariaDB's strong and vibrant community:
mysql_1        | https://mariadb.org/get-involved/
mysql_1        |
mysql_1        | Database initialized
makeproject_1  | Waiting for MySQL server to start...
mysql_1        | MySQL init process in progress...
mysql_1        | 2019-01-24  8:18:05 0 [Note] mysqld (mysqld 10.3.8-MariaDB-1:10.3.8+maria~bionic) starting as process 102 ...
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Using Linux native AIO
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Uses event mutexes
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Number of pools: 1
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Using SSE2 crc32 instructions
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Waiting for purge to start
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: 10.3.8 started; log sequence number 1630815; transaction id 21
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql_1        | 2019-01-24  8:18:05 0 [Note] Plugin 'FEEDBACK' is disabled.
mysql_1        | 2019-01-24  8:18:05 0 [Warning] 'user' entry 'root@a93ea9dc1043' ignored in --skip-name-resolve mode.
mysql_1        | 2019-01-24  8:18:05 0 [Warning] 'user' entry '@a93ea9dc1043' ignored in --skip-name-resolve mode.
mysql_1        | 2019-01-24  8:18:05 0 [Warning] 'proxies_priv' entry '@% root@a93ea9dc1043' ignored in --skip-name-resolve mode.
mysql_1        | 2019-01-24  8:18:05 0 [Note] InnoDB: Buffer pool(s) load completed at 190124  8:18:05
mysql_1        | 2019-01-24  8:18:05 0 [Note] Reading of all Master_info entries succeded
mysql_1        | 2019-01-24  8:18:05 0 [Note] Added new Master_info '' to hash table
mysql_1        | 2019-01-24  8:18:05 0 [Note] mysqld: ready for connections.
mysql_1        | Version: '10.3.8-MariaDB-1:10.3.8+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
apache_1       | 2019-01-24 08:18:06,351 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
apache_1       | 2019-01-24 08:18:06,357 INFO spawned: 'start' with pid 31
apache_1       | 2019-01-24 08:18:06,358 INFO success: rsyslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
apache_1       | 2019-01-24 08:18:06,358 INFO success: apache2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
apache_1       | 2019-01-24 08:18:06,414 INFO exited: start (exit status 1; not expected)
mysql_1        | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
apache_1       | 2019-01-24 08:18:08,421 INFO spawned: 'start' with pid 34
apache_1       | 2019-01-24 08:18:08,476 INFO exited: start (exit status 1; not expected)
mysql_1        | 2019-01-24  8:18:08 10 [Warning] 'proxies_priv' entry '@% root@a93ea9dc1043' ignored in --skip-name-resolve mode.
mysql_1        |
mysql_1        | 2019-01-24  8:18:08 0 [Note] mysqld (initiated by: unknown): Normal shutdown
mysql_1        | 2019-01-24  8:18:08 0 [Note] Event Scheduler: Purging the queue. 0 events
mysql_1        | 2019-01-24  8:18:08 0 [Note] InnoDB: FTS optimize thread exiting.
mysql_1        | 2019-01-24  8:18:08 0 [Note] InnoDB: Starting shutdown...
mysql_1        | 2019-01-24  8:18:08 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
mysql_1        | 2019-01-24  8:18:08 0 [Note] InnoDB: Buffer pool(s) dump completed at 190124  8:18:08
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Shutdown completed; log sequence number 1630824; transaction id 24
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
mysql_1        | 2019-01-24  8:18:10 0 [Note] mysqld: Shutdown complete
mysql_1        |
mysql_1        |
mysql_1        | MySQL init process done. Ready for start up.
mysql_1        |
mysql_1        | 2019-01-24  8:18:10 0 [Note] mysqld (mysqld 10.3.8-MariaDB-1:10.3.8+maria~bionic) starting as process 1 ...
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Using Linux native AIO
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Uses event mutexes
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Number of pools: 1
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Using SSE2 crc32 instructions
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Waiting for purge to start
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: 10.3.8 started; log sequence number 1630824; transaction id 21
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql_1        | 2019-01-24  8:18:10 0 [Note] Plugin 'FEEDBACK' is disabled.
mysql_1        | 2019-01-24  8:18:10 0 [Note] InnoDB: Buffer pool(s) load completed at 190124  8:18:10
mysql_1        | 2019-01-24  8:18:10 0 [Note] Server socket created on IP: '::'.
mysql_1        | 2019-01-24  8:18:10 0 [Warning] 'proxies_priv' entry '@% root@a93ea9dc1043' ignored in --skip-name-resolve mode.
mysql_1        | 2019-01-24  8:18:10 0 [Note] Reading of all Master_info entries succeded
mysql_1        | 2019-01-24  8:18:10 0 [Note] Added new Master_info '' to hash table
mysql_1        | 2019-01-24  8:18:10 0 [Note] mysqld: ready for connections.
mysql_1        | Version: '10.3.8-MariaDB-1:10.3.8+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
apache_1       | 2019-01-24 08:18:11,490 INFO spawned: 'start' with pid 37
apache_1       | 2019-01-24 08:18:11,530 INFO exited: start (exit status 1; not expected)
apache_1       | 2019-01-24 08:18:12,538 INFO gave up: start entered FATAL state, too many start retries too quickly
mysql_1        | 2019-01-24  8:18:15 8 [Warning] Access denied for user 'boincadm'@'172.18.0.3' (using password: NO)
makeproject_1  | Creating database...
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'windows_intelx86', 'Microsoft Windows (98 or later) running on an Intel x86-compatible CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'windows_x86_64', 'Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'i686-pc-linux-gnu', 'Linux running on an Intel x86-compatible CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'x86_64-pc-linux-gnu', 'Linux running on an AMD x86_64 or Intel EM64T CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'powerpc-apple-darwin', 'Mac OS X 10.3 or later running on Motorola PowerPC')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'i686-apple-darwin', 'Mac OS 10.4 or later running on Intel')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'x86_64-apple-darwin', 'Intel 64-bit Mac OS 10.5 or later')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'sparc-sun-solaris2.7', 'Solaris 2.7 running on a SPARC-compatible CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'sparc-sun-solaris', 'Solaris 2.8 or later running on a SPARC-compatible CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'sparc64-sun-solaris', 'Solaris 2.8 or later running on a SPARC 64-bit CPU')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'powerpc64-ps3-linux-gnu', 'Sony Playstation 3 running Linux')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'arm-android-linux-gnu', 'Android running on ARM')
makeproject_1  | added platform: (create_time, name, user_friendly_name) values (1548317896, 'anonymous', 'anonymous')
makeproject_1  | added app: (create_time, name, user_friendly_name) values (1548317896, 'boinc2docker', 'boinc2docker')
makeproject_1  |
makeproject_1  | Found app version directory for: boinc2docker 1.07 windows_x86_64__vbox64_mt
makeproject_1  |
makeproject_1  |     NOTICE: You have not provided a signature file for vm_isocontext_v1.0.0.iso,
makeproject_1  |     and your project's code-signing private key is on your server.
makeproject_1  |
makeproject_1  |     IF YOUR PROJECT IS PUBLICLY ACCESSABLE, THIS IS A SECURITY VULNERABILITY.
makeproject_1  |     PLEASE STOP YOUR PROJECT IMMEDIATELY AND READ:
makeproject_1  |     https://boinc.berkeley.edu/trac/wiki/CodeSigning
makeproject_1  |
makeproject_1  |     Continue (y/n)? cp apps/boinc2docker/1.07/windows_x86_64__vbox64_mt/vm_isocontext_v1.0.0.iso /home/boincadm/project/download/vm_isocontext_v1.0.0.iso
makeproject_1  | cp apps/boinc2docker/1.07/windows_x86_64__vbox64_mt/vboxwrapper_26200_windows_x86_64.exe /home/boincadm/project/download/vboxwrapper_26200_windows_x86_64.exe
makeproject_1  |     Files:
makeproject_1  |         vboxwrapper_26200_windows_x86_64.exe (main program)
makeproject_1  |         vm_isocontext_v1.0.0.iso
makeproject_1  |     Flags:
makeproject_1  |         don't throttle
makeproject_1  |         needs network
makeproject_1  |         API version: 7.9.0
makeproject_1  |     Do you want to add this app version (y/n)?     App version added successfully; ID=1
makeproject_1  | Found app version directory for: boinc2docker 1.07 x86_64-pc-linux-gnu__vbox64_mt
makeproject_1  | cp apps/boinc2docker/1.07/x86_64-pc-linux-gnu__vbox64_mt/vboxwrapper_26198_x86_64-pc-linux-gnu /home/boincadm/project/download/vboxwrapper_26198_x86_64-pc-linux-gnu
makeproject_1  |     Files:
makeproject_1  |         vboxwrapper_26198_x86_64-pc-linux-gnu (main program)
makeproject_1  |         vm_isocontext_v1.0.0.iso
makeproject_1  |     Flags:
makeproject_1  |         don't throttle
makeproject_1  |         needs network
makeproject_1  |         API version: 7.7.0
makeproject_1  |     Do you want to add this app version (y/n)?     App version added successfully; ID=2
makeproject_1  | Found app version directory for: boinc2docker 1.07 x86_64-apple-darwin__vbox64_mt
makeproject_1  | cp apps/boinc2docker/1.07/x86_64-apple-darwin__vbox64_mt/vboxwrapper_26199_x86_64-apple-darwin /home/boincadm/project/download/vboxwrapper_26199_x86_64-apple-darwin
makeproject_1  |     Files:
makeproject_1  |         vboxwrapper_26199_x86_64-apple-darwin (main program)
makeproject_1  |         vm_isocontext_v1.0.0.iso
makeproject_1  |     Flags:
makeproject_1  |         don't throttle
makeproject_1  |         needs network
makeproject_1  |         API version: 7.7.2
makeproject_1  |     Do you want to add this app version (y/n)?     App version added successfully; ID=3
boinc-server-docker_makeproject_1 exited with code 0

Do I need to add any files or anything for the path to work?

Custom validator

Hello! Can you please tell me how I can insert a custom validator into the docker and should I compile it?

Optimize the container

Is it possible to build the BOINC server in another container and use just the artifacts that needed (multi-stage build)? Just like we did with the BOINC Client Intel container?
The production image would be much smaller.

If it's not feasible, than the packages required only for the build should be removed, which also decrease the image size.

Signature Error

When using boinc2docker to generate work the client says
10.07.2016 11:26:26 | ProjectStreet | [error] Signature verification error for boinc2docker_1.03_vbox_job.xml
and
10.07.2016 11:26:26 | ProjectStreet | [error] Checksum or signature error for boinc2docker_1.03_vbox_job.xml

Where can I fix that?

Unable to build server

I tried to do a clean build of a server using the instructions:

git clone https://github.com/marius311/boinc-server-docker.git
cd boinc-server-docker
docker-compose build --no-cache
docker-compose up -d

And a few issues emerged on the "docker-compose build --no-cache" step.

boinc-server-docker/images/makeproject/boinc is empty and thus there is nothing to build
If I checkout boinc to fill that directory, and repeat docker-compose build --no-cache, I then get

Removing intermediate container a467df53a87a
 ---> 49e0a3045cb8
Step 13/32 : COPY boinc2docker /root/boinc2docker
 ---> 798be3ebf02c
Step 14/32 : RUN /root/boinc2docker/boinc2docker_create_app --download_only
 ---> Running in 942b4f2c0bb7
/bin/sh: 1: /root/boinc2docker/boinc2docker_create_app: not found
ERROR: Service 'makeproject' failed to build: The command '/bin/sh -c /root/boinc2docker/boinc2docker_create_app --download_only' returned a non-zero code: 127

Is there something I should be doing different?

Permission error on /results

I just created a new installation of boinc-server-docker with the current master branch,
I noticed that results were not copied to the /results folder of the BOINC server, then found out in the logs that one of the scripts was not able to create the folder /results/boinc2docker due to a permission error.
I created the folder manually and gave write permissions and this fixed the issue, but you might want to take a look into this.

SSL support

I've been trying to add SSL support to my test BOINC project but have been unable to open port 443 fully to the public.

I've tried:

Opening port 443 (ipv4 & ipv6) via UFW on the host vm.
"a2enmod ssl" within the Apache container
Enabled SSL in the /etc/apache2/sites-available/ along with project specific config.
"iptables -A INPUT -p tcp --dport 443 -j ACCEPT" (on host vm, no luck).

I'm going to try next:
"Expose port" in the Apache dockerfile https://docs.docker.com/engine/reference/builder/#/expose

Any tips/tricks/hints?

Cheers

Outdated docker client version

I noticed after entering the apache shell via make exec-apache that the docker client version is quite outdated. From inside the shell, if I run docker version I get the following output:

`Client:
Version: 1.10.3
API version: 1.22
Go version: go1.5.3
Git commit: 20f81dd
Built: Thu Mar 10 21:49:11 2016
OS/Arch: linux/amd64

Server:
Version: 17.06.1-ce
API version: 1.30
Go version: go1.8.3
Git commit: 874a737
Built: Thu Aug 17 22:50:04 2017
OS/Arch: linux/amd64
`

On my host machine I am currently using version 17.06.1-ce for both client and server. There have been many improvements and added features since version 1.10.3. How can I keep the client version up-to-date? I tried using the latest version of boot2docker, but that didn't seem to help. Thanks!

Cannot create new user

Hello,
The server is working fine but when I try to sign up with the BOINC manager or the website it tells me that the email format is invalid.

I tested a lot of emails and none of them work, and they are normal email addresses such as [email protected]

Change default server name from boincserver.com to 127.0.0.1?

From @grctest in BOINC/boinc#1990:

Hey,
Would it be possible to change the default servername from boincserver.com to 127.0.0.1? When set as boincserver.com it breaks the formatting of the default website view until changed. If set to 127.0.0.1 it would work fine. The domain has also been registered recently so it links offsite.
Best regards,CM.

Docker run command does not terminate

I am using the simple example given in the cookbook:

# bin/boinc2docker_create_work.py \ python:alpine python -c "print('Hello BOINC')"

stderr.txt

Error when first running docker-compose up.

When first running docker-compose up -d (under Launching a Test Server), I get the following error:

Step 4 : COPY boinc /root/boinc
---> Using cache
---> 4f5638c0af7b
Step 5 : RUN cd /root/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make
---> Running in b7e087519886
/bin/sh: 1: ./_autosetup: not found
ERROR: Service 'makeproject' failed to build: The command '/bin/sh -c cd /root/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make' returned a non-zero code: 127

I'm able to get past it by running docker-compose pull followed by docker-compose up.

Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux

When upgrading BOINC web server via recompiling - how do you ensure persistent server data?

Hey @marius311,

I make changes to the core BOINC web server (Project-Rain) which require that I self-compile the BOINC web server, given that when you fully stop the docker container the contents of the container are lost, how do I ensure that the mysql databases don't get destroyed when I'm only wanting to uplift the web server code?

Effectively, how do I ensure data persistence for the mysql container when upgrading the core BOINC web server?

Best regards,
CM.

Build errors when testing with python 3

@davidpanderson and @lfield are working on migrating BOINC to python3. See BOINC/boinc#2477

boinc-server-test tries to run its tests against that branch but fails at this step:

Step 1/1 : RUN test -z "$TAG" || boinc2docker_create_app --projhome $PROJECT_ROOT
 ---> Running in 28d9ba77d2f5
Traceback (most recent call last):
  File "/boinc2docker/boinc2docker_create_app", line 185, in <module>
    xmlmerge(src,join(args.projhome,f),idkey=k,mergeat=m)
  File "/boinc2docker/boinc2docker_create_app", line 164, in xmlmerge
    if dc.find(idkey).text==sc.find(idkey).text: break
AttributeError: 'NoneType' object has no attribute 'text'

Would you be able to resolve the issue with this step or provide a flag so that I can skip the step of adding boinc2docker to the docker images when I'm building them for boinc-server-test?

Thanks!

Kevin

boinc_submit does not work within toolbox

I'm just starting out trying to develop a project and in an attempt to get testing as fast as possible I've been trying to use the boinc_submit script.

The container is obviously Linux but I'm wanting to target my windows desktop client so I've not been able to use the single_job_setup script, opting instead to manually create the single_job structure within apps for my platform as per instructions on BOINC site.

The problem is I'm getting a database error when attempting to run the boinc_submit script. After jumping into the source I managed to discover that the problem is it's attempting to insert a workunit, specifying only the name and transition time. The error relates to the lack of a default value for the create_time field. Unfortunately once I'd manually provided the value for that field (converting PHP date to Unix epoch), it only led to the same error for the next field.

As I mentioned I'm new to BOINC and not very experienced. Could anyone offer any pointers about where I might be going wrong? I can see this script is very old ~10 years, is it possible that it no longer works in the latest version?

I've made very few changes to the default boinc-server-docker container, still using the latest tag on the images.

Thanks

Issues with downloading vboxwrapper* and vm_isocontext* files

I have been setting up a boinc server using the boinc-server-docker framework. After editing a few files and using a custom build using the --build option, I was able to successfully launch the server and submit a few jobs, which completed and reported back as well.
To test things further on the client side, I removed the project and added it back again using existing credentials. On submitting some jobs and asking the client to request an update, a new job starts downloading along with all the required files (which got deleted from my local machine while removing the project).
However, the Transfers tab shows that only the layer and similar files are now successfully downloaded. Two files vboxwrapper* and vm_isocontext* get stuck at 0% and the boinc manager keeps retrying periodically (this has happened to both me on my Windows machine as well as a collaborator on his Mac)
On the server side, I tried for eg. from within the project folder

docker-compose down
URL_BASE=http://anthgrid.com PROJECT=dbnupperbound docker-compose up -d --build

This apparently resolved the issue on the Windows machine, although the problem persisted at the Mac end. Hence I later again tried out 1) restarting the physical server, 2) restarting the project as above, 3) detaching/attaching the project from the client side, and the problem has now recurred on the Windows machine as well.

I looked at the event logs generated, and posting the logs post the update request

8/12/2018 10:53:38 AM | dbnupperbound | update requested by user
8/12/2018 10:53:41 AM | dbnupperbound | Sending scheduler request: Requested by user.
8/12/2018 10:53:41 AM | dbnupperbound | Requesting new tasks for CPU
8/12/2018 10:53:46 AM | dbnupperbound | Scheduler request completed: got 1 new tasks
8/12/2018 10:53:48 AM | dbnupperbound | Started download of vboxwrapper_26200_windows_x86_64.exe
8/12/2018 10:53:48 AM | dbnupperbound | Started download of vm_isocontext_v1.0.0.iso
8/12/2018 10:54:10 AM | dbnupperbound | Temporarily failed download of vboxwrapper_26200_windows_x86_64.exe: connect() failed
8/12/2018 10:54:10 AM | dbnupperbound | Backing off 00:02:07 on download of vboxwrapper_26200_windows_x86_64.exe
8/12/2018 10:54:10 AM | dbnupperbound | Temporarily failed download of vm_isocontext_v1.0.0.iso: connect() failed
8/12/2018 10:54:10 AM | dbnupperbound | Backing off 00:02:51 on download of vm_isocontext_v1.0.0.iso
8/12/2018 10:54:10 AM | dbnupperbound | Started download of vbox_job_4f89c783ce0c4f20b908bc4a14059af3.xml
8/12/2018 10:54:10 AM | dbnupperbound | Started download of boinc_app_6aedaa339bb34abe8bf6cd4c457edc43
8/12/2018 10:54:11 AM |  | Project communication failed: attempting access to reference site
8/12/2018 10:54:13 AM |  | Internet access OK - project servers may be temporarily down.
8/12/2018 10:54:15 AM | dbnupperbound | Finished download of vbox_job_4f89c783ce0c4f20b908bc4a14059af3.xml
8/12/2018 10:54:15 AM | dbnupperbound | Finished download of boinc_app_6aedaa339bb34abe8bf6cd4c457edc43
8/12/2018 10:54:15 AM | dbnupperbound | Started download of layer_b4aaa2a9b1c803b2d5e2be58eb77fc258749f3e67bfd9b06677e0c4ec551c580.tar.manual.gz
8/12/2018 10:54:15 AM | dbnupperbound | Started download of layer_a3c77c9bff4b76ebb10c03fdb4412507c07e2229429c322c7e2c505c4391602f.tar.manual.gz
8/12/2018 10:54:16 AM | dbnupperbound | Finished download of layer_a3c77c9bff4b76ebb10c03fdb4412507c07e2229429c322c7e2c505c4391602f.tar.manual.gz
8/12/2018 10:54:16 AM | dbnupperbound | Started download of layer_870d3f402f75021060706f2cbe98030c77db022fd0435e78ba32c9318ce9001c.tar.manual.gz
8/12/2018 10:54:17 AM | dbnupperbound | Finished download of layer_870d3f402f75021060706f2cbe98030c77db022fd0435e78ba32c9318ce9001c.tar.manual.gz
8/12/2018 10:54:17 AM | dbnupperbound | Started download of layer_6a79bf36f57324bd393870cb8e38b5b76814a079f04d31327c131959d17bcbb1.tar.manual.gz
8/12/2018 10:54:18 AM | dbnupperbound | Finished download of layer_6a79bf36f57324bd393870cb8e38b5b76814a079f04d31327c131959d17bcbb1.tar.manual.gz
8/12/2018 10:54:18 AM | dbnupperbound | Started download of layer_b40fae1c32824b69017ffeb2ddb45afaeddec0ef5e0f5b51cc8ecffa1d8c54aa.tar.manual.gz
8/12/2018 10:54:19 AM | dbnupperbound | Finished download of layer_b40fae1c32824b69017ffeb2ddb45afaeddec0ef5e0f5b51cc8ecffa1d8c54aa.tar.manual.gz
8/12/2018 10:54:19 AM | dbnupperbound | Started download of layer_9909df9a616a8748a1bdfc03c1b313b72e53301775b8debd2c6286ffda4be1b8.tar.manual.gz
8/12/2018 10:54:20 AM | dbnupperbound | Finished download of layer_9909df9a616a8748a1bdfc03c1b313b72e53301775b8debd2c6286ffda4be1b8.tar.manual.gz
8/12/2018 10:54:20 AM | dbnupperbound | Started download of layer_8dbde8905f7ed067e8e2995167ccfbc558bf7e9ce77df8e9ce36aab2615f4007.tar.manual.gz
8/12/2018 10:54:43 AM | dbnupperbound | Finished download of layer_b4aaa2a9b1c803b2d5e2be58eb77fc258749f3e67bfd9b06677e0c4ec551c580.tar.manual.gz
8/12/2018 10:54:43 AM | dbnupperbound | Started download of layer_2af2c0deefccd67415d414df5f933d6f0d852637908a9d19c894c1dc26b0ef09.tar.manual.gz
8/12/2018 10:54:44 AM | dbnupperbound | Finished download of layer_2af2c0deefccd67415d414df5f933d6f0d852637908a9d19c894c1dc26b0ef09.tar.manual.gz
8/12/2018 10:54:44 AM | dbnupperbound | Started download of layer_01217b14ec2f229cd6c54e5656e5e002189d08d6252353547bd402ceeba727c8.tar.manual.gz
8/12/2018 10:55:18 AM | dbnupperbound | Finished download of layer_01217b14ec2f229cd6c54e5656e5e002189d08d6252353547bd402ceeba727c8.tar.manual.gz
8/12/2018 10:55:18 AM | dbnupperbound | Started download of layer_34321bb08c5f29ab0ac24fb1770e8fc2f5bc56e1a4d93816814b535b206ffdfa.tar.manual.gz
8/12/2018 10:55:22 AM | dbnupperbound | Finished download of layer_8dbde8905f7ed067e8e2995167ccfbc558bf7e9ce77df8e9ce36aab2615f4007.tar.manual.gz
8/12/2018 10:55:22 AM | dbnupperbound | Finished download of layer_34321bb08c5f29ab0ac24fb1770e8fc2f5bc56e1a4d93816814b535b206ffdfa.tar.manual.gz
8/12/2018 10:55:22 AM | dbnupperbound | Started download of image_04d415dc1215f3d7814c90573df9d0f77aaeec1624b6e2087ffeb8bd5877a2ad.tar.manual.gz
8/12/2018 10:55:23 AM | dbnupperbound | Finished download of image_04d415dc1215f3d7814c90573df9d0f77aaeec1624b6e2087ffeb8bd5877a2ad.tar.manual.gz
8/12/2018 10:56:17 AM | dbnupperbound | Started download of vboxwrapper_26200_windows_x86_64.exe
8/12/2018 10:56:39 AM | dbnupperbound | Temporarily failed download of vboxwrapper_26200_windows_x86_64.exe: connect() failed
8/12/2018 10:56:39 AM | dbnupperbound | Backing off 00:05:53 on download of vboxwrapper_26200_windows_x86_64.exe
8/12/2018 10:56:40 AM |  | Project communication failed: attempting access to reference site
8/12/2018 10:56:42 AM |  | Internet access OK - project servers may be temporarily down.
8/12/2018 10:57:01 AM | dbnupperbound | Started download of vm_isocontext_v1.0.0.iso
8/12/2018 10:57:24 AM | dbnupperbound | Temporarily failed download of vm_isocontext_v1.0.0.iso: connect() failed
8/12/2018 10:57:24 AM | dbnupperbound | Backing off 00:07:19 on download of vm_isocontext_v1.0.0.iso
8/12/2018 10:57:25 AM |  | Project communication failed: attempting access to reference site
8/12/2018 10:57:26 AM |  | Internet access OK - project servers may be temporarily down.
8/12/2018 11:02:33 AM | dbnupperbound | Started download of vboxwrapper_26200_windows_x86_64.exe
8/12/2018 11:02:55 AM |  | Project communication failed: attempting access to reference site
8/12/2018 11:02:55 AM | dbnupperbound | Temporarily failed download of vboxwrapper_26200_windows_x86_64.exe: connect() failed
8/12/2018 11:02:55 AM | dbnupperbound | Backing off 00:12:18 on download of vboxwrapper_26200_windows_x86_64.exe
8/12/2018 11:02:57 AM |  | Internet access OK - project servers may be temporarily down.

I tried to check the apache logs on the server, but they point to /dev/stdout and /dev/stderr hence haven't been able to check them.
On trying to check logs from the host environment, for eg. docker logs dbnupperbound_apache_1, I get several reap messages at the end

...
...
2018-08-12 05:00:04,014 CRIT reaped unknown pid 1348)
2018-08-12 05:00:04,112 CRIT reaped unknown pid 1339)
2018-08-12 05:00:04,113 CRIT reaped unknown pid 1341)
2018-08-12 05:00:04,113 CRIT reaped unknown pid 1343)
2018-08-12 05:00:04,114 CRIT reaped unknown pid 1345)
2018-08-12 05:00:04,114 CRIT reaped unknown pid 1347)

Given that most task files are getting downloaded, it seems I am missing something obvious, but haven't been able to figure it out. Great if you could point in the right direction.

EDIT:
Also, an approach which had worked in the past, but haven't been able to replicate this time. I tried a hard reset by first backing up the mysql database, then using docker-compose down -v, then the normal up -d --build command, and then restoring the mysql database. Post that a project detach/attach at the client side. While all the user and workunit information is retained, and again the Transfers tab shows the layer files getting downloaded, the two v* files stay at 0%.

EDIT2:
On a replica vm, I followed all the steps except importing the mysql backup, and it worked! Ofcourse this cannot be a feasible option once a project has run for some aount of time, hence I have been searching for a series of steps to use in a crisis scenario, before scaling things up.
In the main server, there have been some abandoned tasks over the past 2 days, and some tasks which are still in progress but pending the v* file transfer. Is it possible these are creating some kind of bottleneck?

$PROJHOME

What or where is $PROJHOME ?

Feature request: add variables to server_makeproject image

Hi, I'm trying out your dockerized boinc and it seems to work just fine except one little moment.
Image boinc/server_makeproject uses hardcoded parameters.
It would be really good for automation if they were defined as evironment variables like $PROJHOME you already have.

In that case you can generate ready-to-run projects like:
docker run --rm -e URL_BASE=http://myserver.net -e DB_HOST=some_mysql_container .... boinc/server_makeproject

Docker-compose pull failing on Ubuntu 20.04 server

When following the README.md file and get to the docker-compose pull command I receive the following error.

Step 6/32 : RUN cd /usr/local/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make
 ---> Running in b778c889767b
/bin/sh: 1: ./_autosetup: not found
ERROR: Service 'makeproject' failed to build: The command '/bin/sh -c cd /usr/local/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make' returned a non-zero code: 127

Ubuntu 20.04 headless server.

404 Not Found for 127.0.0.1/boincserver

After setting up boinc on the machine, I get the following 404 Not found while accessing http://127.0.0.1/boincserver :

To reproduce:

git clone https://github.com/marius311/boinc-server-docker.git
cd boinc-server-docker
docker-compose pull
docker-compose up -d

OS : Ubuntu 18.04
Docker version: 19.03.6

Please help on the same.

Log rotation doesn't work until log_*/.old is created

Handle large docker images

I currently have a very large docker image to run my application, it is ~1GB uncompressed,
I'm trying to reduce it further but for now I'd like to make some tests as is.

I see that my BOINC jobs go out of disk space when uncompressing the layers.
Where can I increase space of the images so that this is able to run?

How do I change de hard coded URL?

I tried scanning the repository and changed them all but it still doesnt work when you sign in

Docker tasks not pushed to clients

Hi Marius,
Very nice your project!

I am struggling to have the task pushed to the clients
I am creating the task as per your example:

root@boincserver:~/project# bin/boinc2docker_create_work.py python:alpine python -c "print('Hello BOINC')"
Automatically setting memory allocation for job to 680MB.
Automatically setting disk allocation for job to 145MB.
Image already imported into BOINC. Reading existing info...
Creating input template for job...
workunit name: boinc2docker_18737_1626799878.359693

But seems that nothing is pushed into the client

I am using the app Android I downloaded 7.16.16.apk

And while the app is running correctly the Rosetta tasks (downloading and executing), adding my server url to the app, is always "WAITING FOR JOB"

as the server is not launching any jobs

in the server I have 42 jobs I created from command line, but the client is not downloading anything

boinc2docker: 42
Tasks ready to send: 42

in the download subdir in the server there are a lot of files already generated and ready to be picked up, very likely, but the client app is not reacting

Can you suggest me please what to do server side to push the jobs to the clients ecosystem?
Really appreciated!

Steven

Multiple Failures - apache, docker-compose, boincserver

Hi,

I've been trying to get this running on Fedora 33 (with docker) and I'm hitting multiple roadblocks (following instructions from https://github.com/marius311/boinc-server-docker/blob/master/docs/cookbook.md).

Apache 404 Error. (when navigating to 127.0.0.1/boincserver or /boincserver)

This one happens both from localhost and trying to access from LAN. Apache is running here.
Tried the workaround from (#53 (comment)) and it gives:


boincserver is temporarily shut down for maintenance. Please try again later.

Powered by BOINC

©2020 REPLACE WITH COPYRIGHT HOLDER

TAG="" docker-compose up -d

Yields the same error from #65. Though doing TAG="" docker-compose pull first then doing TAG="" docker-compose up -d solves this particular issue but the result is the same as the previous one, apache fails to work.

How to reproduce

clone this repo
follow commands from https://github.com/marius311/boinc-server-docker/blob/master/docs/cookbook.md

Software

$ docker-compose -v
docker-compose version 1.27.4, build unknown
$ docker --version 
Docker version 19.03.13, build 4484c46

constraints.sql doesn't appear to be applied

Greetings,

It appears that when a new project is created using the makeproject.sh script doesn't appear to run the constraints.sql from database.create_database (or at least, I don't see any of the constraints on the database after creating a new project).

Thanks for taking a look!

Kevin

problem with boinc2docker

Docker crashes with "couldn't start app: Can't link input file" Any Idea why? I ran bin/boinc2docker_create_work.py mtrnord/docker-benchmark:latest sh -c "sysbench --debug --test=threads > /root/shared/results/benchmark.txt" && bin/sign_all_apps

Problems with job Schedule

Hello, we have a Problem with the Jopb Scheduling. We can't get any Jobs to the Clients. Is this an Issue or are we doing something wrong?

Unable to find results.tgz

Great project! I'm not sure if this is an issue or if I'm just confused. I followed your setup and ran through you basic cookbook examples successfully, but I'm having trouble with the following:

root@boincserver:~/project# bin/boinc2docker_create_work.py
python:alpine python -c "open('/root/shared/results/hello.txt','w').write('Hello BOINC')"

My BOINC client is able to download and execute the above command, and from the boincserver_ops admin page I can see the stderr out:
...
Guest Log: Saving results...
Guest Log: hello.txt
...

but I'm not able to find this file. My understanding is that hello.txt should be zipped in a file called results.tgz and found in the /results volume of my Apache server (accessed via make exec-apache). However, I'm not seeing it. Is it somehow being deleted? Am I missing something?

/bin/sh: 1: ./_autosetup: not found

Error:

Step 4 : COPY boinc /root/boinc
 ---> f55b8d9f00f5
Removing intermediate container 9f5723a5fb2b
Step 5 : RUN cd /root/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make
 ---> Running in 733335984fdb
/bin/sh: 1: ./_autosetup: not found
ERROR: Service 'makeproject' failed to build: The command '/bin/sh -c cd /root/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make' returned a non-zero code: 127

Installed docker-compose version 1.8, ran the 'docker-compose up -d' command during the test project setup, encountered the above error.

MySQL connection issues on initial test deployment from cookbook

thanks @marius311 for providing this! I'd like to use it for a BOINC project I'm helping to build.

I just cloned the repository and followed the instructions until docker-compose up -d, but I get 404:

wget http://127.0.0.1/boincserver
--2018-03-27 18:22:49--  http://127.0.0.1/boincserver
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-03-27 18:22:49 ERROR 404: Not Found.

I think this is due to the project container having issues connecting to MySQL:

Updating project files in data volume...
Waiting for MySQL server to start...
ERROR 1130 (HY000): Host '172.17.0.3' is not allowed to connect to this MySQL server
Creating database...                                                                                                                Traceback (most recent call last):
  File "<string>", line 5, in <module>                                                                                              
  File "/root/boinc/py/Boinc/database.py", line 283, in create_database
    connect(config, nodb=True)                                                                                                        File "/root/boinc/py/Boinc/database.py", line 270, in connect
    passwd=config.__dict__.get('db_passwd', ''))
  File "/root/boinc/py/Boinc/db_base.py", line 498, in do_connect                                                                   
    passwd=passwd, cursorclass=MySQLdb.cursors.DictCursor)                                                                          
  File "/usr/lib/python2.7/dist-packages/MySQLdb/__init__.py", line 81, in Connect
    return Connection(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 187, in __init__
    super(Connection, self).__init__(*args, **kwargs2)
_mysql_exceptions.OperationalError: (1130, "Host '172.17.0.3' is not allowed to connect to this MySQL server")

would you have any suggestions?

some other info below:

docker ps
CONTAINER ID        IMAGE                                 COMMAND                  CREATED              STATUS              PORTS                NAMES
1fea3c4994c9        boinc/server_apache:latest-b2d        "docker-php-entrypoi…"   54 seconds ago       Up 40 seconds       0.0.0.0:80->80/tcp   boincserverdocker_apache_1
e6197c79adbb        boinc/server_makeproject:latest-b2d   "/bin/sh -c /root/ma…"   54 seconds ago       Up 41 seconds                            boincserverdocker_makeproject_1
19a9101b93ba        boinc/server_mysql:latest             "docker-entrypoint.s…"   About a minute ago   Up 53 seconds       3306/tcp             boincserverdocker_mysql_1

Docker version

docker --version
Docker version 18.03.0-ce, build 0520e24
docker-compose --version
docker-compose version 1.20.1, build 5d8c71b

Apache logs

docker logs 1fea3c4994c9
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2018-03-27 22:25:37,113 CRIT Supervisor running as root (no user in config file)
2018-03-27 22:25:37,113 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2018-03-27 22:25:37,123 INFO RPC interface 'supervisor' initialized
2018-03-27 22:25:37,124 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-03-27 22:25:37,124 INFO supervisord started with pid 1
2018-03-27 22:25:38,127 INFO spawned: 'cron' with pid 7
2018-03-27 22:25:38,133 INFO spawned: 'start' with pid 8
2018-03-27 22:25:38,136 INFO spawned: 'rsyslogd' with pid 9
2018-03-27 22:25:38,143 INFO spawned: 'apache2' with pid 10
2018-03-27 22:25:39,301 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-03-27 22:25:39,301 INFO success: start entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-03-27 22:25:39,301 INFO success: rsyslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-03-27 22:25:39,301 INFO success: apache2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Build error because of expired certificate

"Connecting to psysh.org (psysh.org)|185.199.111.153|:443... \u001b[0m\u001b[91mconnected.", "\u001b[0m\u001b[91mERROR: The certificate of 'psysh.org' is not trusted.", "ERROR: The certificate of 'psysh.org' has expired."

Full log is here:
https://github.com/BOINC/boinc/pull/4545/checks?check_run_id=3813645743

Change the master url

I notice that the url after building is 127.0.0.1/boincserver, how can I change it to 127.0.0.1? I tried to modify config.xml but failed. In addition, I encountered permission issue when trying to access the root directory of Apache server, https://stackoverflow.com/questions/41337917/wamp-forbidden-you-dont-have-permission-to-access-on-this-server-apache-2. How can I build a server with master url set to root of hostname?

Security improvements

The default configuration is aimed at getting the server fully functional with no extra steps needed, but leaves the server in a highly insecure state. Somehow this should be improved. Some things which will need consideration:

mysql password
ops password
signing keys
???

Permission error when building images on Windows

Mentioned here #9 (comment), the output looks something like:

Step 5 : RUN cd /root/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make
---> Running in 86884f9a5dca
/bin/sh: 1: ./_autosetup: Permission denied
ERROR: Service 'makeproject' failed to build: The command '/bin/sh -c cd /root/boinc && ./_autosetup && ./configure --disable-client --disable-manager && make' returned a non-zero code: 126

I believe its related to Docker Toolbox on Windows. I'd be interested in knowing if this happens on Mac with Docker Toolbox, or if it happens with Docker for Windows. Will investigate...

make assimilated results files have .tgz extension

Using 'root' user accounts instead of non-root user within docker containers?

Hey,

I've been messing around with boinc-server-docker trying to make my own project and noticed that within the dockerfile images you're using the user 'root' instead of a non-root user.

Do you think we should use non-root user accounts within the containers to increase security?

Cheers,
CM.

How to debug a failing job

I have successfully deployed boinc-server-docker on a server with the included test project, I created a client using https://github.com/BOINC/boinc-client-docker (installing also VirtualBox).

I created a job with:

bin/boinc2docker_create_work.py \
python:alpine python -c "open('/root/shared/results/hello.txt','w').write('Hello BOINC')"

I see the job is sent to the client and executed, however it logs:

30-Mar-2018 13:02:18 [boincserver] Computation for task boinc2docker_3766_1522410497.503524_1 finished
30-Mar-2018 13:02:18 [boincserver] Output file boinc2docker_3766_1522410497.503524_1_r1095010587_0.tgz for task boinc2docker_3766_1522410497.503524_1 absent

How do I find out what is wrong with this application?
I have all the details of the deployment in the draft of the tutorial I'm writing, see https://zonca.github.io/2018/03/boinc-server-jetstream.html

ERROR: Version in "./docker-compose.yml" is unsupported.

ubuntu@VM-0-16-ubuntu:~/boinc-server-docker$ docker-compose pull
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

ubuntu@VM-0-16-ubuntu:~/boinc-server-docker$ docker version
Client:
 Version:      17.03.2-ce
 API version:  1.27
 Go version:   go1.6.2
 Git commit:   f5ec1e2
 Built:        Thu Jul  5 23:07:48 2018
 OS/Arch:      linux/amd64
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.27/version: dial unix /var/run/docker.sock: connect: permission denied
ubuntu@VM-0-16-ubuntu:~/boinc-server-docker$ docker-compose version
docker-compose version 1.8.0, build unknown
docker-py version: 1.9.0
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016

what should i do?

Forbidden You don't have permission to access / on this server.

I got the issue when try to open the browser with 127.0.0.1:80

Forbidden
You don't have permission to access / on this server.
Apache/2.4.25 (Debian) Server at 127.0.0.1 Port 80

I am using MAC here.

Virtual Machine hangs on dhcp

I have identified the problem on one of the machines where I am testing the client with Virtualbox, it just hangs at the DHCP request, see log below.
Would you have suggestions on how to fix this?

00:12:53.682441 VMMDev: Guest Log: Setting hostname to boot2docker Done. 
00:12:53.685723 VMMDev: Guest Log: Fri May 18 06:51:34 UTC 2018 dhcp ------------------------------- 
00:12:55.622708 NAT: Link up 
00:12:58.905592 VMMDev: Guest Log: udevadm settle - timeout of 5 seconds reached, the event queue contains: 
00:12:58.907497 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0700:00 (1136) 
00:12:58.908945 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00 (1368) 
00:12:58.910227 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:00 (1369) 
00:12:58.911554 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:01 (1370) 
00:12:58.912876 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:02 (1371) 
00:12:58.914200 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:03 (1372) 
00:12:58.915522 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:04 (1373) 
00:12:58.917289 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:05 (1374) 
00:12:58.918650 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:06 (1375) 
00:12:58.920183 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:07 (1376) 
00:12:58.921535 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:08 (1377) 
00:12:58.922901 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:09 (1378) 
00:12:58.924278 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:0a (1379) 
00:12:58.926112 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:0b (1380) 
00:12:58.927770 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:0c (1381) 
00:12:58.929099 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:0d (1382) 
00:12:58.930082 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:0e (1383) 
00:12:58.931168 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXCPU:0f (1384) 
00:12:58.933137 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXPWRBN:00 (1385) 
00:12:58.934582 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 (1386) 
00:12:58.935687 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0 (1387) 
00:12:58.937076 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSLPBN:00 (1388) 
00:12:58.938557 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1 (1389) 
00:12:58.940165 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1/event1 (1390) 
00:12:58.941627 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00 (1391) 
00:12:58.943082 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 (1392) 
00:12:58.944687 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00 (1393) 
00:12:58.946624 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/ACPI0003:00/power_supply/AC (1394) 
00:12:58.948047 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00 (1395) 
00:12:58.949221 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/device:01 (1396) 
00:12:58.950447 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input6 (1397) 
00:12:58.951941 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input6/event4 (1398) 
00:12:58.954220 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0400:00 (1399) 
00:12:58.956060 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0400:01 (1400) 
00:12:58.958219 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:00 (1401) 
00:12:58.960040 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:01 (1402) 
00:12:58.961851 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:02 (1403) 
00:12:58.963676 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0501:03 (1404) 
00:12:58.965466 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:00 (1405) 
00:12:58.967483 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C0A:00 (1406) 
00:12:58.969248 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP8390:00 (1407) 
00:12:58.971026 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00 (1408) 
00:12:58.972863 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/APP0001:00 (1409) 
00:12:58.974787 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0000:00 (1410) 
00:12:58.976760 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0100:00 (1411) 
00:12:58.978726 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0103:00 (1412) 
00:12:58.980048 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0200:00 (1413) 
00:12:59.001664 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0303:00 (1414) 
00:12:59.002894 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0700:00 (1415) 
00:12:59.004107 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0B00:00 (1416) 
00:12:59.005298 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0F03:00 (1417) 
00:12:59.006529 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02 (1418) 
00:12:59.007873 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:00 (1419) 
00:12:59.009374 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:01 (1420) 
00:12:59.010870 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:02 (1421) 
00:12:59.012374 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:03 (1422) 
00:12:59.013776 VMMDev: Guest Log:   /sys/devices/LNXSYSTM:00/LNXSYBUS:01 (1423) 
00:12:59.933666 VMMDev: Guest Log: Fri May 18 06:51:40 UTC 2018 dhcp -------------------------------

Running the BOINC jobs directly inside a docker container

Hi
I'm wondering if there is a way for not using the VirtualBox while submitting boinc2docker jobs.
I'm looking for a mechanism for running jobs directly inside a Docker container instead of running them in VirtualBox
Thanks

Docker image constraints

I am looking for guidance on how to set some image values so as to facilitate job execution. Of particular interest are entrypoint, cmd, and workingdir. How should these be set to allow execution for cases where input files have arbitrary names? My understanding is that BOINC will manage file transfer and put all input files in a common fixed directory location. The fixed directory location can then be mounted as a docker volume again at a fixed location.

Can working directory be set to the fixed location inside the docker container?
Can entrypoint refer to a script in the working directory? (It would exist in the image)
cmd could be used to pass variable arguments to the entrypoint.

Running the command will produce output files. The documentation implies such outputs should be put in a separate results directory to be transfered back to the BOINC host. Applications will typically write results in the working directory. Is there a mechanism to run a post processing script in the container to move results to different location?

Upgrading and misc issues

From @davidpanderson:

Marius:
Steve Clark and I were working with a container-based BOINC server and we ran into a snag:
we need to update the server software in the main container.
In order to do this, the container needs to have:

git
a copy of the BOINC repo
all the gnu tools (gcc, autoconf, etc)
a text editor

It looks like you made the container fairly stripped-down to minimize size.
But in this case size isn't a big concern.

Other issues:

It looks like make_project creates a download directory that's owned by root
and is not writable by the Apache user (www-data);
it needs to be writable remote file management to work.
It looks like there's an assumption that the container has a single project, in /project.
Some of the BOINC tools (like "upgrade") assume that projects are subdirectories
of ~/projects.

Apache Issue

Hello, everyone! I am setting up my server on a Raspberry Pi 3 and I have a problem with Apache. When I run command docker-compose up -d I got this:

$  docker-compose up -d
Starting boinc-server-docker_mysql_1       ... done
tarting boinc-server-docker_makeproject_1 ... done
Starting boinc-server-docker_apache_1      ... done

But If I go to 127.0.0.1/boincserver and the server doesn't work. There is another interesting thing: Apache service is not working too. If I try to start Apache.service, the initialization fails. What should I do?

Boinc client unable to properly communicate with BOINC server (internal 500 error)

Hey,

I've been making some good progress with my BOINC project, but I've run into an issue with my project:
https://github.com/grctest/project-rain-site/issues/2

This is preventing me from properly connecting to my project within the BOINC manager client - the account name and team fields do not appear as a result.

My main aim is to provide the ability to match one's CPID (which needs to merge with other project's CPIDs) to multiple cryptocurrency addresses/accounts, so distributing work units isn't planned at the moment.

Without work units, will I continue to encounter this 'internal 500 error'? Or has something else potentially caused this issue?

I'm going to re-fork the boinc-server-docker repo with the aim of not breaking.. what I may have broken.. lol..

Cheers.

Documentation

Hello,

I was reading the documentation (https://github.com/marius311/boinc-server-docker/blob/master/docs/cookbook.md) and I think that in "Custom config.xml and other files" section it should be:
docker-compose run makeproject cat config.xml > myproject/images/makeproject/config.xml
instead of:
docker-compose run makeproject cat config.xml > images/makeproject/config.xml

Thank you

This was very helpful for me. Much appreciated

Add a license file

Can you please add a license file? It would be helpful to clarify for people what permissions are required to use this library. Thanks!