-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
component: local appmeta: staleThis issue/PR is stale and will be closed soonThis issue/PR is stale and will be closed soonself-hostedteam: IDEtype: bugSomething isn't workingSomething isn't working
Description
Bug description
Per https://community.gitpod.io/t/local-companion-and-self-hosted-docker-image/4351/3.
When using a v0.10.0-1 Docker Image build of Gitpod, the Local Companion app does not seem to work. From what I can tell, the Oauth Authorize endpoint in the Docker Image either does not exist or is not configured to accept requests.
The following error is displayed on the browser window that is opened when running the Local Companion app:
Steps to reproduce
- Build and run Docker Image with Docker Compose -
docker-compose.yaml
version: '3'
services:
gitpod:
image: eu.gcr.io/gitpod-core-dev/build/gitpod-k3s@sha256:b3280468152027221dfa109bf7c0753dd1dfec9bdd66057b076eb0b0890b336c
privileged: true
restart: unless-stopped
volumes:
- gitpod-docker:/var/gitpod/docker
- gitpod-docker-registry:/var/gitpod/docker-registry
- gitpod-minio:/var/gitpod/minio
- gitpod-mysql:/var/gitpod/mysql
- gitpod-workspaces:/var/gitpod/workspaces
- ./values:/values
- ./certs:/certs
ports:
- 443:443
- 80:80
environment:
- DOMAIN=[your domain]
volumes:
gitpod-docker:
gitpod-docker-registry:
gitpod-minio:
gitpod-mysql:
gitpod-workspaces:
- Run Local Companion app with Gitpod host specified:
./gitpod-local-companion-linux --gitpod-host="[your domain]"
Expected behavior
Local Companion app connects and allows for usage.
Example repository
None.
Anything else?
Please let me know if you need any further info to get this specific setup working.
Metadata
Metadata
Assignees
Labels
component: local appmeta: staleThis issue/PR is stale and will be closed soonThis issue/PR is stale and will be closed soonself-hostedteam: IDEtype: bugSomething isn't workingSomething isn't working
