Zhenyang Zhao

@ly5156 Could you please take a look at this issue？

We need to redesign this page, will discuss with you in detail later

@sniperking1234 You can follow the 0.6.0 milestone progress, which will be released once we complete the issues in the milestone.

Good advice, we will add more providers later

Yes, We have not enough quota to do pull request GitHub action e2e test, reuse drone and do e2e testing in tag stage is better. Dapper has a certain learning...

@doublefx Thanks for your feedback! Try changing the volume mounts path `/var/run/docker.sock:/var/run/docker.sock:ro` like this: ``` services: nginx-proxy: image: nginxproxy/nginx-proxy container_name: nginx-proxy ports: - "80:80" volumes: - /var/run/docker.sock:/var/run/docker.sock:ro autok3s: image: cnrancher/autok3s:v0.6.0...

This should be a bug in `k3d` provider. Only the default socket path is considered here, and the custom `DOCKER_HOST` env is not open to configure. You can try to...

Try this docker compose(which only running autok3s container with host port mapping), then access ui using `http://127.0.0.1:`: ``` services: autok3s: image: cnrancher/autok3s:v0.6.0 init: true ports: - 8080 volumes: - /var/run/docker.sock:/var/run/docker.sock:ro...

I will support enviroment `DOCKER_HOST` feature as soon as possible to support this scenario.

Can your environment access the Internet? I try on my environment and the pods can be pulled down. Unfortunately I think `0.6.0` is a failed version, it is recommended to...