Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Labs Play with K8s - out of space #194

Open
ingerul91 opened this issue Jul 16, 2024 · 4 comments
Open

Labs Play with K8s - out of space #194

ingerul91 opened this issue Jul 16, 2024 · 4 comments

Comments

@ingerul91
Copy link

ingerul91 commented Jul 16, 2024

Hello everyone.

We have the following issue when using the virtual environment provided on https://labs.play-with-k8s.com/

-> Click on Start -> On the new session I've added a new instance by selecting Add New Instance -> and if we want to go with the setup for https://github.com/collabnix/kubelabs/blob/master/kube101.md - by cloning the repository - git clone https://github.com/collabnix/kubelabs we get the following error below.


[node1 ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
overlay 10G 68K 10G 1% /
tmpfs 64M 0 64M 0% /dev
tmpfs 16G 0 16G 0% /sys/fs/cgroup
> /dev/sdb 64G 64G 20K 100% /etc/hosts
shm 64M 0 64M 0% /dev/shm

[node1 ~]$ git clone https://github.com/collabnix/kubelabs
Cloning into 'kubelabs'...
error: copy-fd: write returned No space left on device
fatal: cannot copy '/usr/share/git-core/templates/description' to '/root/kubelabs/.git/description': No space left on device


Also yesterday and the day before I was able to clone the repo and wanted to start the bootstrap.sh but again I ran over the space issue. Is there a way to correct this?

I've also attached screenshots.
session_01
session_02

If this is not the right place to raise this issue please tell me and I will open it accordingly.

Thank you.

Best Regards,
Ozzy

@ingerul91
Copy link
Author

@ajeetraina Hello. Do you know how to fix the above?

Thank you.
BR,
Ozzy

@ajeetraina
Copy link
Collaborator

@ingerul91 It looks like there were a few changes made to those instances to restrict it from consuming CPU and memory. We might need to suggest users to use their own Kubernetes cluster rather than sticking to PWK platform.

@ajeetraina
Copy link
Collaborator

The other way I was thinking to pushing our users to Killercoda.

@ingerul91
Copy link
Author

Thank you for your suggestion. I was not aware of Killercoda. Yes it would be good if we had the 2 suggestion you made put onto the main page so that at least any person knows that the old environments are no longer to be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants