You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix:point_right:: double check masters and nodes can access each other at any port!
Not only ssh(22) port but also api-server(6443) and many others as different serivces/pods needs different ports open. Especially checking security group when using aws/aliyun infras. Currently we suggest allow all2all under internal/private vpc/subnets.
Storage requirements rela
Summary
Description
Cause
Issue
PR
Status
Download Image Fail
sealos run CLusterImage fail
lack of disk spaces
π
Download Image Fail
sealos build still fail while pulling an image from the private registry
Here are some common install/run questions.
status meaning:
Root permission rela
root
Usersudo sealos run
not works wellroot
user, currently donot support run assudoers
orrootless
Fix:point_right:: using
root
user to exec commands.sealos run
without any ipssealos run
must spec at least one master and one nodeFix:point_right:: using atleast two machine(or multipass to start vms quickly)
System environment rela
invalid argument "never" for " --pull" flag: strconv. ParseBool: parsing "never": invalid syntax
sealos run
commandbuildah
installed but version do not match sealos's requirementFix:point_right:: Delete System's
buildah
and using sealos's build-in version.apparmor_parser
file not founddisableApparmor=false
, Update Image versionsealos reset
ed clustercontainer runtime is not running
ortoken exit status 1
and similar errorssealos reset
donot clearly cleaned all System enviromentsFix:point_right:: Upgrade to 4.1.4-rc1 and above!
Network connective rela
couldn't validate the identity of the API Server
, something like10.103.97.2:6443
fail*.tar.gz
*.tar.gz
offline image packageοΌmake offline installation easierhostname
under cluster fileetcd
clusterkubeadm
to customizeFix:point_right:: double check masters and nodes can access each other at any port!
Not only ssh(22) port but also api-server(6443) and many others as different serivces/pods needs different ports open. Especially checking
security group
when using aws/aliyun infras.Currently we suggest allow
all2all
under internal/private vpc/subnets.Storage requirements rela
sealos run CLusterImage
failsealos build still fail while pulling an image from the private registry
sealos default install on root home dir but want to change this location
Fix:point_right:: add more storages and/or memories!
After install and run
--cmd
not work--cmd
except to merge build-in commandserror converting YAML to JSON
*.yaml.tmpl
file to*.yaml.tmpl.bak
, as.tmpl
suffix file will be rendered by defaultmaster0
master
s failsealctl token
do not synced or expiredFix:point_right:: Upgrade to 4.1.4-rc1 and above!
Cluster image rela
digest failed
cilium
, have digest inside, sealos build will failmissing
, witch do not update for local's already pulled imageFix:point_right:: Upgrade to 4.1.4-rc1 and above!
ingress-nginx
pod keepspending
env
env
vars pass to ClusterImage to override tepmlateskuboard
install failkuboard
with tested kubernetes versionPodSecurityPolicy
kubernetes:v1.25
withcalico
labring/calico:v3.24.1
Before contributing to docs, please check out docs contributing guide.
The text was updated successfully, but these errors were encountered: