MedCo Technical Documentation
GithubDocker HubMedCoLDS
v0.3.0
v0.3.0
  • Home
  • Releases
  • For System Administrators
    • Requirements
    • Deployment
      • Local Test Deployment
      • Network Test Deployment
      • Network Production Deployment
      • Configuration
        • Keycloak
        • HTTPS Configuration
        • Configuring SwitchAAI Authentication
    • Data Loading
      • v0 (Genomic Data)
      • v1 (I2B2 Demodata)
    • Command-Line Interface (CLI)
    • Network Architecture
    • Common Problems
  • For Developers
    • Local Development Deployment
    • System Architecture
    • Description of the default test data
    • Database
Powered by GitBook
On this page
  • Docker-related issues
  • Changing the Docker default address pool
  • Using Docker as non-root user

Was this helpful?

Export as PDF
  1. For System Administrators

Common Problems

PreviousNetwork ArchitectureNextLocal Development Deployment

Last updated 5 years ago

Was this helpful?

Docker-related issues

Changing the Docker default address pool

If after deploying MedCo you notice some connectivity problems on your machine, or on the opposite the running containers have connectivity problems, check for potential conflict between your machine networks and Docker's virtual network (e.g. with ifconfig). If you do have such conflicts, you can edit Docker's configuration to set the addresses to use. Example:

/etc/docker/daemon.json
{
  "default-address-pools": [{
      "base": "10.10.0.0/16",
      "size": 24
  }]
}

Using Docker as non-root user

If you get such an error message while trying to execute commands as a non-root user:

docker: Got permission denied while trying to connect to the Docker daemon socket at ...

You will need to follow .

these instructions from the Docker official documentation