Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[self-hosted] Support for Docker 20.10 #6021

Closed
jgallucci32 opened this issue Oct 4, 2021 · 3 comments
Closed

[self-hosted] Support for Docker 20.10 #6021

jgallucci32 opened this issue Oct 4, 2021 · 3 comments
Labels
meta: stale This issue/PR is stale and will be closed soon self-hosted

Comments

@jgallucci32
Copy link
Contributor

jgallucci32 commented Oct 4, 2021

This issue is to track the required changes to make Docker 20.10 work for self-hosted installation. It was fixed in production and reported in issue #3051 but does not work for self-hosted (yet).

Error when running Docker 20.10 on Gitpod 0.10.0

$ docker run hello-world
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "proc" to rootfs at "/proc" caused: mount through procfd: operation not permitted: unknown.
ERRO[0003] error waiting for container: context canceled

Current workaround is to downgrade to Docker 19.03. This can be done with the following custom workspace image

FROM gitpod/workspace-full

RUN sudo apt-get update && sudo apt-get purge -y \
         docker-ce \
         docker-ce-cli \
         containerd.io && \
    sudo apt-get install -y \
         docker-ce=5:19.03.15~3-0~ubuntu-focal \
         docker-ce-cli=5:19.03.15~3-0~ubuntu-focal && \
    sudo apt-get clean && sudo rm -rf /var/lib/apt/lists/* && \
    sudo curl -fsSL -o /usr/bin/runc https://github.com/opencontainers/runc/releases/download/v1.0.0-rc93/runc.amd64

Thanks to @asthomasdk for posting this workaround on Discord.

@MasonM
Copy link

MasonM commented Nov 2, 2021

I ran into this issue too on EKS, but the workaround didn't seem to work. This seems to be the same bug as gitpod-io/gitpod-eks-guide#25

@jgallucci32
Copy link
Contributor Author

@MasonM Try adding this to your answers.yaml for the chart

defaults:
  dnsPolicy: ClusterFirstWithHostNet

I added this some time ago to the self-hosted install on RKE to address the issue with NodePorts and HostPorts and incorrect DNS resolution. Not sure if it is related, but I thought it might be worth a try.

@stale
Copy link

stale bot commented Feb 5, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Feb 5, 2022
@stale stale bot closed this as completed Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon self-hosted
Projects
None yet
Development

No branches or pull requests

3 participants