Closed winrey closed 4 years ago
Hi there, thanks for opening this issue. However, this doesn't seem to be an issue with k3d (probably not even with k3s), but rather with your specific setup.
I don't have the
/boot/cmdline.txt
and try to create it withcgroup_memory=1 cgroup_enable=memory
, but it doesn't work. What exactly does this mean? You couldn't create the file? Or k3d/k3s still didn't work after a reboot after applying those changes? You can check the section Enable container features on this post https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/ for the cmdline.txt settings (Note: the file only has one line, no linebreaks/CRs).
Closing this due to inactivity
INFOMATION
How was the cluster created?
sudo k3d create
What did you do afterwards?
k3d get-kubeconfig --name='k3s-default'
What did you expect to happen?
Print the config file path.
Screenshots or terminal output
Which OS & Architecture?
Which version of
k3d
?Which version of docker?
DESCRIPTION
I try to create a cluster and failed. The creating log seems well but there is nothing when excute
docker ps
. I cannot got config file by excutek3d get-kubeconfig --name='k3s-default'
either.I found latter that the container meet an error and exited.
Here is the logs:
Creating
Get Config File
Container log
I don't have the
/boot/cmdline.txt
and try to create it withcgroup_memory=1 cgroup_enable=memory
, but it doesn't work.Check config