-
Notifications
You must be signed in to change notification settings - Fork 944
Closed
Labels
kind/bugThis is bug report for projectThis is bug report for project
Description
Question
When I want to process allinone_aliyun.sh to create a kubernetes cluster with the pouch(version 1.1.0), I find the error message as below:
Hit:1 http://mirrors.ustc.edu.cn/ubuntu bionic InRelease
Hit:2 http://mirrors.ustc.edu.cn/ubuntu bionic-updates InRelease
Hit:3 http://mirrors.aliyun.com/opsx/pouch/linux/debian pouch InRelease
Hit:4 http://mirrors.ustc.edu.cn/ubuntu bionic-backports InRelease
Hit:5 http://mirrors.ustc.edu.cn/ubuntu bionic-security InRelease
Hit:6 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial InRelease
Hit:7 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
Hit:8 https://download.docker.com/linux/ubuntu bionic InRelease
Reading package lists... Done
N: Skipping acquire of configured file 'stable/binary-i386/Packages' as repository 'http://mirrors.aliyun.com/opsx/pouch/linux/debian pouch InRelease' doesn't support architecture 'i386'
Hit:1 http://mirrors.ustc.edu.cn/ubuntu bionic InRelease
Hit:2 http://mirrors.aliyun.com/opsx/pouch/linux/debian pouch InRelease
Hit:3 http://mirrors.ustc.edu.cn/ubuntu bionic-updates InRelease
Hit:4 http://mirrors.ustc.edu.cn/ubuntu bionic-backports InRelease
Hit:5 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial InRelease
Hit:6 http://mirrors.ustc.edu.cn/ubuntu bionic-security InRelease
Hit:7 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease
Hit:8 https://download.docker.com/linux/ubuntu bionic InRelease
Reading package lists... Done
N: Skipping acquire of configured file 'stable/binary-i386/Packages' as repository 'http://mirrors.aliyun.com/opsx/pouch/linux/debian pouch InRelease' doesn't support architecture 'i386'
Reading package lists... Done
Building dependency tree
Reading state information... Done
pouch is already the newest version (1.1.0-0ubuntu16).
0 upgraded, 0 newly installed, 0 to remove and 139 not upgraded.
Synchronizing state of pouch.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable pouch
update-rc.d: error: pouch Default-Start contains no runlevels, aborting.
My pouch.service
[Unit]
Description=pouch
[Service]
ExecStart=/usr/local/bin/pouchd --enable-cri=true --cri-version=v1alpha2
ExecReload=/bin/kill -HUP $MAINPID
Type=notify
# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TimeoutStartSec=0
# set delegate yes so that systemd does not reset the cgroups of pouch containers
Delegate=yes
# kill only the pouch process, not all processes in the cgroup
KillMode=process
# restart the pouch process if it exits prematurely
Restart=on-failure
StartLimitBurst=3
StartLimitInterval=60s
[Install]
WantedBy=multi-user.target
Metadata
Metadata
Labels
kind/bugThis is bug report for projectThis is bug report for project