I’m trying to setup Harness CD Community in my home lab for testing. I installed harness via docker-compose on an Ubuntu 20.04 VM. When I go to add a delegate via docker method it never connects. I suspect that is do to the below configuration it is having me run. Looking at harness docs it states about created a delegate profile and id assume that’s where I’d change the URLs to point to correct locations but I can seem to find where to set that up in the interface? Would someone be able to point me in the correct direction to get the delegate up and running?
version: "3.7" services: harness-ng-delegate: restart: unless-stopped deploy: resources: limits: cpus: "0.5" memory: 768M image: harness/delegate:latest environment: - ACCOUNT_ID=asdfasdfasdfasdfasdfasdfasdfasdf - ACCOUNT_SECRET=asdfasdfasdfasdfasdfasdfasdfasdfasdf - MANAGER_HOST_AND_PORT=http://host.docker.internal - WATCHER_STORAGE_URL=http://host.docker.internal/storage/wingswatchers - WATCHER_CHECK_LOCATION=watcherprod.txt - REMOTE_WATCHER_URL_CDN=https://qa.harness.io/public/shared/watchers/builds - DELEGATE_STORAGE_URL=http://host.docker.internal/storage/wingsdelegates - DELEGATE_CHECK_LOCATION=delegateprod.txt - USE_CDN=false - CDN_URL=https://qa.harness.io - DEPLOY_MODE=KUBERNETES_ONPREM - DELEGATE_NAME=test - NEXT_GEN=true - DELEGATE_DESCRIPTION= - DELEGATE_TYPE=DOCKER - DELEGATE_TAGS= - DELEGATE_TASK_LIMIT=50 - DELEGATE_ORG_IDENTIFIER=default - DELEGATE_PROJECT_IDENTIFIER=test - PROXY_MANAGER=true - VERSION_CHECK_DISABLED=false - INIT_SCRIPT=echo "Docker delegate init script executed."