Portainer Templates logo

Portainer Templates

Boinc Boinc

Science

BOINC is a platform for high-throughput computing on a large scale (thousands or millions of computers). It can be used for volunteer computing (using consumer devices) or grid computing (using organizational resources). It supports virtualized, parallel, and GPU-based applications.

Image details

Pulls: 1.2M
Architectures: amd64, arm64
Image size: 1.0 GB
Latest: 8.2.8
User: linuxserver
Created: Mar 16, 2020
Updated: 6 days ago
Status: active

Configuration

Type
Container
Platform
linux
Image
linuxserver/boinc:latest
Ports
8080:8080/tcp8181:8181/tcp
Volumes
/config : /srv/lsio/boinc/config
Env vars
PUID=1000PGID=1000TZ=Etc/UTCPASSWORD=
Restart
unless-stopped

Template by technorabilia

Notes

Portainer App Templates by Technorabilia, based on data provided by LinuxServer.io.

Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.

mkdir -p /srv/lsio/boinc/config

Installation

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

docker run -d --name Boinc \
  -p 8080:8080/tcp \
  -p 8181:8181/tcp \
  -e 'PUID=1000' \
  -e 'PGID=1000' \
  -e 'TZ=Etc/UTC' \
  -e 'PASSWORD=' \
  -v /srv/lsio/boinc/config:/config \
  --restart=unless-stopped \
  linuxserver/boinc:latest

Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.

services:
  boinc:
    image: linuxserver/boinc:latest
    ports:
      - 8080:8080/tcp
      - 8181:8181/tcp
    volumes:
      - /srv/lsio/boinc/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      PASSWORD: ''
    restart: unless-stopped

Save this file as boinc-stack.yml, then from a manager node, run docker stack deploy -c boinc-stack.yml boinc

version: '3.8'
services:
  boinc:
    image: linuxserver/boinc:latest
    ports:
      - 8080:8080/tcp
      - 8181:8181/tcp
    volumes:
      - /srv/lsio/boinc/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      PASSWORD: ''
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

boinc-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: boinc
  labels:
    app: boinc
spec:
  replicas: 1
  selector:
    matchLabels:
      app: boinc
  template:
    metadata:
      labels:
        app: boinc
    spec:
      containers:
        - name: boinc
          image: linuxserver/boinc:latest
          env:
            - name: PUID
              value: '1000'
            - name: PGID
              value: '1000'
            - name: TZ
              value: Etc/UTC
            - name: PASSWORD
              value: ''
          ports:
            - containerPort: 8080
              protocol: TCP
            - containerPort: 8181
              protocol: TCP
          volumeMounts:
            - name: boinc-data-0
              mountPath: /config
      volumes:
        - name: boinc-data-0
          hostPath:
            path: /srv/lsio/boinc/config

boinc-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: boinc
spec:
  type: LoadBalancer
  selector:
    app: boinc
  ports:
    - name: 8080-tcp
      port: 8080
      targetPort: 8080
      protocol: TCP
    - name: 8181-tcp
      port: 8181
      targetPort: 8181
      protocol: TCP

Save this file as ~/.config/containers/systemd/boinc.container

[Unit]
Description=Boinc

[Container]
Image=linuxserver/boinc:latest
ContainerName=boinc
PublishPort=8080:8080/tcp
PublishPort=8181:8181/tcp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Environment=PASSWORD=
Volume=/srv/lsio/boinc/config:/config

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start boinc

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

linuxserver/boinc

This readme has been truncated from the full version found HERE

BOINC is a platform for high-throughput computing on a large scale (thousands or millions of computers). It can be used for volunteer computing (using consumer devices) or grid computing (using organizational resources). It supports virtualized, parallel, and GPU-based applications.

Application Setup

The container can be accessed at:
  • https://yourhost:8181/

Usage

docker run -d \
  --name=boinc \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e PASSWORD= `#optional` \
  -p 8080:8080 \
  -p 8181:8181 \
  -v /path/to/boinc/config:/config \
  --device /dev/dri:/dev/dri `#optional` \
  --shm-size="1gb" \
  --restart unless-stopped \
  lscr.io/linuxserver/boinc:latest

Serve Boinc on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying boinc.example.com to http://Boinc:8080

Add this to your Caddyfile

boinc.example.com {
	reverse_proxy http://Boinc:8080
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs Boinc
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8080 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8080
  • Stop the other service, or pick a different host port. In 8080:8080 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Boinc can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /srv/lsio/boinc/config
  • Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull linuxserver/boinc:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect Boinc --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Required settings are blank

PASSWORD has no default value, and Boinc may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

Similar apps

Foldingathome Foldingathome Science