Configure crictl correctly in Vagrant testbed (#3278)

Set endpoints correctly for containerd to avoid error logs. Signed-off-by: Antonin Bas <[email protected]>
antrea-io · Feb 9, 2022 · bef46cf · bef46cf
1 parent 5ccd3d1
commit bef46cf
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/test/e2e/infra/vagrant/playbook/roles/common/tasks/containerd.yml b/test/e2e/infra/vagrant/playbook/roles/common/tasks/containerd.yml
@@ -61,3 +61,8 @@
     daemon_reload: yes
     state: restarted
   when: containerd_config.changed
+
+- name: Configure crictl
+  template:
+    src: templates/crictl.yaml.j2
+    dest: /etc/crictl.yaml
diff --git a/test/e2e/infra/vagrant/playbook/roles/common/templates/crictl.yaml.j2 b/test/e2e/infra/vagrant/playbook/roles/common/templates/crictl.yaml.j2
@@ -0,0 +1,2 @@
+runtime-endpoint: unix:///run/containerd/containerd.sock
+image-endpoint: unix:///run/containerd/containerd.sock