"ClientCertPath": "/Users/lenok/.docker/machine/certs/cert.pem", "ClientKeyPath": "/Users/lenok/.docker/machine/certs/key.pem", "ServerKeyPath": "/Users/lenok/.docker/machine/machines/default/server-key.pem", "ServerCertPath": "/Users/lenok/.docker/machine/machines/default/server.pem", "CaPrivateKeyPath": "/Users/lenok/.docker/machine/certs/ca-key.pem", "CaCertPath": "/Users/lenok/.docker/machine/certs/ca.pem", "CertDir": "/Users/lenok/.docker/machine/certs", "StorePath": "/Users/lenok/.docker/machine", "SSHKeyPath": "/Users/lenok/.docker/machine/machines/default/id_rsa", I've also checked the space occupied by /mnt/sda1, which is 2.9GB. I think I upgraded docker-machine which may have fixed it.īoot2Docker version 1.9.1, build master : cef800b - Fri Nov 20 19:33:įilesystem Size Used Available Use% Mounted onĬgroup 1001.3M 0 1001.3M 0% /sys/fs/cgroup We have a lot more containers 20 so definitely try to diagnose with lenadroid's info.Īlso mine may be resolved now, still confirming. We have a cleanup script which gets rid of unused stuff but it doesn't seem to help.
I had to blow it away and start with a fresh machine. I restarted my machine and afterwards I couldn't even ssh in with docker because it didn't come up right.
#Docker for mac disk full install#
I had tried to install sqlite3 to troubleshoot things and couldn't because tmp was full: Provide additional info you think is important: Provide additional environment details (AWS, VirtualBox, physical, etc.): Use the commands below to provide key information from your environment: This is an automated, informational response.įor more information about reporting issues, see We will, however, reopen it if you later provide the information. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
You can ensure this by searching the issue list for this repository. If you are reporting a new issue, make sure that we do not have any duplicates already open. Please read this important information about creating issues.
What is the correct way to resolve the issue with space limits here?ĭocker images command gives the following output:
So the issue is definitely in some Docker settings related to sizing. When I remove all my cassandra ones and leave just a couple of Debian - java is able to be extracted from the tar. I think the issue isn't in some unused containers that take space, the issue is more in the amount of space that should be increased.Īre there any limits that Docker has to run the containers? It is present when I run "docker ps -a" - in the "exited" state. I have that container, that doesn't show up by the command "docker ps -s". That container for Cassandra is called node-1, which isn't on the list. No space left on device" - error message shown for this attempt. In went to check to Kitematic and found out that it is in the DOWN state and I can't start it: "Cannot write node-1. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES SIZEĩd8029e21918 debian:latest "/bin/bash" 54 minutes ago Up 54 minutes deb-2 620.5 MB (virtual 744 MB)Ĥ9c7a0e37475 debian:latest "/bin/bash" 55 minutes ago Up 55 minutes deb-1 620 MB (virtual 743.5 MB)Ħ6a17af83ca3 cassandra "/docker-entrypoint.s" 4 hours ago Up 4 hours 7000-7001/tcp, 7199/tcp, 9042/tcp, 9160/tcp node-2 40.16 MB (virtual 412.6 MB)Īfter seeing that output I noticed that one of my nodes with cassandra is missing.
0 kommentar(er)
