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

Ability to configure containerd config.toml #331

Closed
deniseschannon opened this issue Apr 11, 2019 · 1 comment
Closed

Ability to configure containerd config.toml #331

deniseschannon opened this issue Apr 11, 2019 · 1 comment
Labels
kind/enhancement An improvement to existing functionality
Milestone

Comments

@deniseschannon
Copy link

Look at existing PRs to get it in:
#248
#264

@dnoland1
Copy link
Contributor

dnoland1 commented May 4, 2019

Before changing containerd template, verified it was listening on port 10010:

root@k3s-node1:/var/lib/rancher/k3s/agent/etc/containerd# netstat -anp | grep 10010
tcp        0      0 127.0.1.1:10010         0.0.0.0:*               LISTEN      9936/containerd

Copied /var/lib/rancher/k3s/agent/etc/containerd/config.toml to config.toml.tmpl. Edited config.toml.tmpl and changed stream_server_port = "10011".
Restarted k3s. Confirmed containerd is now listening on port 10011:

root@k3s-node1:/var/lib/rancher/k3s/agent/etc/containerd# netstat -anp | grep 10011
tcp        0      0 127.0.1.1:10011         0.0.0.0:*               LISTEN      13906/containerd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement An improvement to existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants