Closed ccll closed 2 years ago
same issue here, did you solve it?
@shaoye Nope, still waiting the canonical solution.
Right now I workaround this by manually docker build & docker push
to a container registry and reference the pushed image there.
Same issue here and the aforementioned workaround wouldn't work for our use cases. Could someone from GitPod Team help here, please?
we switched to Ubuntu 2004 and it worked
@ccli & @seenox what is your containerd version (ctr version
)?
I'm tracking down info so we can get a resolution on this.
@mrzarquon Sorry for the late reply.
Here is my ctr version
Client:
Version: 1.4.4
Revision: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
Go version: go1.13.15
Server:
Version: 1.4.4
Revision: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
UUID: 8c3f8d28-fa9a-429b-8a5c-ee3d7954b79c
@ccll Hi, thanks for your information. Can you open this repository in your gitpod?
https://github.com/utam0k/gitpod-playground/tree/eStargz
https://${your_gitpod}/#https://github.com/utam0k/gitpod-playground/tree/eStargz
This issue is brought into by eStargz. Fortunately, we just removed it. https://github.com/gitpod-io/gitpod/pull/9492
@mrzarquon @utam0k sorry for the late reply (and bumping the issue).
Here is my ctr version
:
Client:
Version: 1.5.4
Revision: 69a4a55aa42353c71aae40e5bb27a412d8e3149b
Go version: go1.13.15
Server:
Version: v1.4.6
Revision: d71fcd7d8303cbf684402823e425e9dd2e99285d
UUID: e092e812-9a86-44ad-b6b0-dbec0f674629
And I'm not able to open the example repository.
Checked in v2022.4.2
, installed using kots
.
@Seenox cc: @gitpod-io/engineering-self-hosted Thanks for your confirmation. It's turned out that the version of contained is probably irrelevant. The main branch has already included fixed PR. So, please wait for releasing the latest self-hosted version. If you will get the same error with the latest main branch, please feel free to reopen this issue.
Confirmed the issue was fixed in release-2022.05.0.5. :heart:
Also confirming the issue has been fixed. Thanks!
Bug description
My
.gitpod.Dockerfile
builds successfully with runningdocker build ...
directly in workspace container, but failed to build after commited to git and started a new workspace based on that new commit.Related logs:
Steps to reproduce
My host environment:
(I know that only Ubuntu is officially supported, but my host is a legacy one and are running many production services on it now, and since Gitpod can almost run without much problem on it, I think there might be a way to make Debian as a community supported distro for Gitpod.)
Installed kernel 5.10 from buster-backports.
Kubernetes is a single node k3s cluster.
Gitpod installer config file:
.gitpod.yml
.gitpod.Dockerfile
Workspace affected
No response
Expected behavior
The docker image should build successfully just like running
docker build ...
in workspace container.Example repository
No response
Anything else?
No response