Description
Bug description
The evidence for this is entirely anecdotal. This is more an investigation ticket as opposed to something with a clearly defined outcome
Request createWorkspace failed with message: 13 INTERNAL: cannot resolve workspace image: hostname required
Unknown Error: { "code": -32603 }
In Discord, we have seen a steady increase in the number of people reporting the above error message when using EKS. This issue usually is a result of a connectivity failure between the workspace and the container registry - most likely either incorrect credentials, a TLS cert error.
AWS container registry deviates from the Docker v2 API spec - if the repo doesn't exist, the spec says to create the repo which AWS does not do - so we use the internal registry with S3 storage behind it.
When I ask users to comment out containerRegistry.s3storage, the threads are usually abandoned implying that this has solved the issue.
containerRegistry:
inCluster: true
s3storage:
bucket: bucket-name
certificate:
kind: secret
name: object-storage-gitpod-tokenSteps to reproduce
This task is to investigate the following:
- Is the guide providing the correct secrets?
- Is the S3 storage in the Installer correctly implemented?
If either of those are yes, the task then becomes the work to fix these issues.
If not, it's likely a question of documentation in the EKS guide - perhaps we're not highlighting the purpose of these credentials and they're providing the wrong credentials/wrong IAMs. This process SHOULD be automated, but it may be that there's an undocumented step that's already taken place in the Gitpod AWS account that we need to communicate to users.
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response