Skip to content

cniweb/srbminer-multi-docker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

85 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

srbminer-multi-docker

High performance, open source CPU & AMD GPU Miner Docker Image. Mine up to 4 different algorithms/coins at the same time!

Snyk Container Docker Image CI Docker Pulls

Usage from ghcr.io

docker run ghcr.io/cniweb/srbminer-multi:latest

https://github.com/cniweb/srbminer-multi-docker/pkgs/container/srbminer-multi

Usage from Docker.io

docker run docker.io/cniweb/srbminer-multi:latest

Usage from Quay.io

docker run quay.io/cniweb/srbminer-multi:latest

Development and CI/CD

GitHub Secrets Configuration

To enable automated Docker image building and pushing to multiple registries, configure the following GitHub Secrets in your repository settings:

Required Secrets for Registry Access:

  1. Docker Hub (docker.io):

    • DOCKER_USERNAME: Your Docker Hub username
    • DOCKER_PASSWORD: Your Docker Hub password or access token
  2. GitHub Container Registry (ghcr.io):

    • GITHUB_TOKEN: Automatically provided by GitHub Actions with packages: write permission configured in the workflow
    • No manual secret configuration needed - the workflow automatically grants the necessary permissions
  3. Quay.io:

    • QUAY_USERNAME: Your Quay.io username
    • QUAY_PASSWORD: Your Quay.io password or robot token

How to Configure Secrets:

  1. Go to your repository on GitHub
  2. Click on SettingsSecrets and variablesActions
  3. Click New repository secret
  4. Add each secret with the exact name shown above

Note: For GitHub Container Registry, the GITHUB_TOKEN is automatically provided by GitHub Actions and configured with the necessary packages: write permission in the workflow file. No manual configuration is required.

Registry Behavior:

  • The build script will automatically detect which registry credentials are available
  • If credentials for a registry are missing, that registry will be skipped
  • At least one registry must be configured for the build to proceed
  • The build will fail if no valid registry credentials are provided

Manual Building:

You can also run the build script locally by setting the appropriate environment variables:

export DOCKER_USERNAME="your_username"
export DOCKER_PASSWORD="your_password"
export GITHUB_TOKEN="your_github_token"
export QUAY_USERNAME="your_quay_username"
export QUAY_PASSWORD="your_quay_password"

./build.sh