Message boards : Number crunching : Geppetto Test 001 - Segnalazioni e Commenti
Message board moderation
Author | Message |
---|---|
Send message Joined: 22 Jan 25 Posts: 2 Credit: 4 RAC: 0 |
Thread ufficiale per discutere del primo test dell'applicazione "Geppetto Boinc" |
Send message Joined: 7 Feb 25 Posts: 4 Credit: 807 RAC: 80 |
Downloaded docker and then ran sudo ln -s /usr/bin/docker /bin/unknown All tasks result in error. I have installed buildx and will try again. Still getting errors. running docker command: ps --all --filter "name=boinc__boinc.llmentor.org_llmentorgrid__batch_18__job_wu525_0" permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/json?all=1&filters=%7B%22name%22%3A%7B%22boinc__boinc.llmentor.org_llmentorgrid__batch_18__job_wu525_0%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied command output: creating container boinc__boinc.llmentor.org_llmentorgrid__batch_18__job_wu525_0 running docker command: images |
Send message Joined: 6 Feb 25 Posts: 8 Credit: 12,258 RAC: 876 |
Installed on Fedora 41 system and all worked successfully. Work unit ran for 4 minutes wall clock. Used 16.6G virtual and 1.1G resident memory. During python phase it used as many as 26 processors at times. Note: the front page is missing the step identified by sabayonine to add boinc to the docker group usermod -aG docker boinc. The system will need to be rebooted after the usermod command to set the group change. |
Send message Joined: 7 Feb 25 Posts: 4 Credit: 807 RAC: 80 |
Note: the front page is missing the step identified by sabayonine to add boinc to the docker group usermod -aG docker boinc. The system will need to be rebooted after the usermod command to set the group change. Thanks, will try again after changing permissions. Edit: Done that but now no tasks available. |
Send message Joined: 6 Feb 25 Posts: 8 Credit: 12,258 RAC: 876 |
On the EPYC server, I have limited the other boinc work to 64 processors (approximately) and created an app_config.xml file for the LLMentorGrid project limiting it to 1 work unit at a time. LLMentorGrid work can have access to the other 64 threads. I'll run with this configuration for a while to see how everything responds and to determine if there is any slow down in the other work. |
Send message Joined: 22 Jan 25 Posts: 12 Credit: 56 RAC: 5 |
That's interesting because I hadn't had the possibility to test it on machines with many threads. I will probably choose the plan class "mt" for this application so that it's going to use multithreading, now I think it's kind of cheating because even though it is set as single thread then the docker will use all the available threads. |
Send message Joined: 6 Feb 25 Posts: 3 Credit: 9,614 RAC: 929 |
In reply to entity's message of 7 Feb 2025: [...]Note: the front page is missing the step identified by sabayonine to add boinc to the docker group usermod -aG docker boinc. The system will need to be rebooted after the usermod command to set the group change. You don't need to restart your computer, you can just restart the docker service. For ubuntu: sudo systemctl restart boinc-client.service |
Send message Joined: 6 Feb 25 Posts: 3 Credit: 9,614 RAC: 929 |
Tried another batch of wu...and new errors for me. The host is a dual xeon E5-2699 v3 with ubuntu 24.04.1 The wu run for a while then it exits with an error saying running docker command: create --name boinc__boinc.llmentor.org_llmentorgrid__batch_19__job_wu1149_0 -v .:/app -e ARGS="" boinc_geppetto_test_ver_1 Error response from daemon: create .: volume name is too short, names should be at least two alphanumeric characters command output: starting container running docker command: start boinc__boinc.llmentor.org_llmentorgrid__batch_19__job_wu1149_0 Error response from daemon: No such container: boinc__boinc.llmentor.org_llmentorgrid__batch_19__job_wu1149_0 Error: failed to start containers: boinc__boinc.llmentor.org_llmentorgrid__batch_19__job_wu1149_0 Example 1 and Example 2 Also, in the stderr all containers on the host will be shown. Including those not related to the project |
Send message Joined: 6 Feb 25 Posts: 3 Credit: 9,614 RAC: 929 |
In reply to Corla99 [Lombardia]'s message of 7 Feb 2025: You don't need to restart your computer, you can just restart the docker service. For ubuntu:sudo systemctl restart boinc-client.service I pasted the wrong command, this is the correct one: sudo systemctl restart docker.service |
Send message Joined: 6 Feb 25 Posts: 8 Credit: 12,258 RAC: 876 |
Good to know. Thanks That makes it quite a bit simpler and less intrusive Side Note: Doesn't seem to be picked up by WUProp@Home. Probably because it doesn't run under the boinc id but as root in the docker container or because it runs as something WUProp doesn't recognize. |
Send message Joined: 7 Feb 25 Posts: 3 Credit: 358,712 RAC: 21,618 |
In reply to Corla99 [Lombardia]'s message of 7 Feb 2025: In reply to Corla99 [Lombardia]'s message of 7 Feb 2025: Tried that still getting all errors, even rebooted tried it again but still errors ... sudo systemctl restart docker.service steve@PBOYZTOY02L:~$ sudo systemctl restart docker.service [sudo] password for steve: Failed to restart docker.service: Unit docker.service not found. |
Send message Joined: 8 Feb 25 Posts: 11 Credit: 506,452 RAC: 41,992 |
When trying to set usermod I get this on several PCs. usermod: group 'docker' does not exist |
Send message Joined: 6 Feb 25 Posts: 8 Credit: 12,258 RAC: 876 |
In reply to STE\/E's message of 8 Feb 2025: In reply to Corla99 [Lombardia]'s message of 7 Feb 2025: Was the docker installation successful? The systemd service is installed as part of the docker install. |
Send message Joined: 6 Feb 25 Posts: 8 Credit: 12,258 RAC: 876 |
In reply to mmonnin's message of 8 Feb 2025: When trying to set usermod I get this on several PCs. Was the docker installation successful? The docker group is created by the docker install process. |
Send message Joined: 7 Feb 25 Posts: 3 Credit: 358,712 RAC: 21,618 |
I did the Docker installation procedure from the front page the only command that actually worked was the 1'st command "sudo apt-get install docker.io" & I don't get the Docker not installed error. The other commands were rejected, still get error's though even with Docker installed, I did the restart docker command, rebooted & tried the start Docker command again but still just errors ... I stopped work on all my Linux box's but 1 until this get sorted out ... |
Send message Joined: 8 Feb 25 Posts: 3 Credit: 265,425 RAC: 14,480 |
error. <core_client_version>7.24.1</core_client_version> |
Send message Joined: 22 Jan 25 Posts: 12 Credit: 56 RAC: 5 |
Hi fzs600, this looks like the "classical" permission error. Before being able to run docker workunits using boinc, you need to give permissions to the user boinc to use docker. This can be done with the command: usermod -aG docker boinc and, if it still doesn't work, usermod -aG docker <username>where username it's your username (it depends on how boinc is installed, but the first case should be much more popular. I saw that you just get a "geppetto-hf-inference" workunits: these are new workunits that I am still testing, probably in some hours I will put a news item in the home page about this new app. |
![]() Send message Joined: 7 Feb 25 Posts: 8 Credit: 33,666 RAC: 2,909 |
When I do the Docker.io install I get these error messages: W: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/c/containerd-app/containerd_1.7.12-0ubuntu2~20.04.1_amd64.deb 404 Not Found [IP: 185.125.190.82 80] W: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/universe/d/docker.io-app/docker.io_24.0.7-0ubuntu2~20.04.1_amd64.deb 404 Not Found [IP: 185.125.190.82 80] mikey |
Send message Joined: 22 Jan 25 Posts: 12 Credit: 56 RAC: 5 |
This looks like a problem related with your Ubuntu distribution: perhaps it's too old (20.04) and Docker cannot be found into the archives. Did you try to sudo apt-get updatebefore? Otherwise, you can use the official installation procedure from the Docker webpage: https://docs.docker.com/engine/install/ubuntu/: # Add Docker's official GPG key: sudo apt-get update sudo apt-get install ca-certificates curl sudo install -m 0755 -d /etc/apt/keyrings sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc sudo chmod a+r /etc/apt/keyrings/docker.asc # Add the repository to Apt sources: echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \ $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}") stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin However, I suspect that the wrapper is not going to run on Ubuntu 20.04: now it is compiled with a new version of GLIBC and probably will refuse too run on such an old distribution. Solving this problem is on my list, I need to recompile the wrapper so that it can runs even on older distribution. |
Send message Joined: 8 Feb 25 Posts: 3 Credit: 265,425 RAC: 14,480 |
In reply to manalog's message of 8 Feb 2025: Hi fzs600, this looks like the "classical" permission error. ok 8 Feb 2025, 15:09:18 UTC 8 Feb 2025, 15:14:59 UTC Terminé et validé 47.87 73.07 1.89 geppetto-hf-inference v1.00 (mt) |
©2025 Matteo Rinaldi