I installed ddev on my macbook. I initiated a drupal7 project and wanted to proceed with the db import. However, this import could not complete due to lack of disk size.
What would be the best way to increase the available disk size?
I do have more than 100GB available on my laptop, but the database container doesn't seem to take not of that available space.
SSH-ing into the project (ddev ssh), I noticed that the partition for mysql was full...
thx
it's apparantly as easy as going to the preferences screen of your Docker Desktop and increase the disk size of the vm there...
You just change the size of the disk allocation for Docker.
On Docker Desktop (macOS and Win10 Pro) this is under the "advanced" section of the preferences or settings menu. This is non-destructive.
On Docker Toolbox (Win 10 Home typically), you set up the docker-machine with the size you want, as shown in the docs - I don't think there's a way to increase the disk size on Docker Toolbox without it being essentially a factory reset.
Related
For installing docker on windows home edition , there are two options if I don't want to run virtual machine.
Which is better :
installing docker desktop ?
installing using wsl2 ?
I'm not going to answer which one is better but instead present some points you should consider before choosing one. However, if you're using Windows Home Edition, I'm afraid your choice is to either:
upgrade to Windows Pro and install Docker with the original Windows backend
install WSL2, then install Docker with the WSL2 backend
This is mentioned on the Docker website. Instructions for Windows Home/WSL2 here and for Windows Pro/Non-WSL2 here.
Bind mount performance
If you care about bind-mounts, where you share a directory between the host OS filesystem (Windows) and the container filesystem (usually Linux), you'll want to compare performance between these two options.
If you want faster bind-mount performance on WSL2, you should mount shared files in the Linux filesystem (the part of your system dedicated to WSL2) for mounting. So you'd want to use \\wsl$\Ubuntu-18.04\home\<user name>\Project instead of C:\Users\<user name>\Project. Docker has more info about this here and Microsoft has more info here.
Start time
Other points mentioned on the Docker website include that Docker has a faster cold-start time with the WSL2 backend compared to the previous version.
Changing Docker system settings
Using WSL2, you'll also have to modify the WSL2 configuration if you want to reduce the amount of memory Docker can use for example. See details here as referenced from the Docker on WSL2 best practices.
I see no two options, at least in the terms you used stating the questions.
On Windows 10 you install Docker Desktop and this can have WSL2 as backend.
On Windows 10 Home, specifically, you can install Docker Desktop with WSL2 backend.
For reference see "Install Docker Desktop on Windows Home" documentation page where only one option is described, and not two.
Docker For Mac is demanding 4GB of available RAM.
That is a much larger overhead than I have seen before for VMs.
Is there any way to run Docker on Mac without so much RAM?
Have you tried these settings - https://docs.docker.com/docker-for-mac/#advanced
I have been running Docker Desktop on Mac with these settings for a long time without no issues until you run some heavy workloads on it.
My question is: If you use Docker tool box (that is required for windows 10 home to run Docker) you are essentially using a virtual machine (vm)?
If you are using a vm already the only reason to use docker from that point is to save on many more multiple instances?
Meaning if you only want 1 extra (guest instance): you can have a vm. Though, with docker (toolbox on windows 10 home) you would have 1 vm and it runs docker?
The only way that is useful is if you want many more instances as in: 1 vm + 1 docker or + 1000 more dockers?
Or am I missing something?
Yes, docker toolbox uses Oracle VirtualBox cause Windows 7, 8, and Windows 10 home cannot use Hyper V. And yes, If you are using a VM already the only reason to use docker from that point is to save on many more multiple instances but it also allows easy backup and deployment. But you are losing a decent amount of memory when running a VM and then even more when you are running docker.
So although Docker CE will tell you your Windows doesn't support Hyper-V, this isn't always the case (if you check in System Info you might have Hyper-V enabled, if you're on an Insider build or many builds on GPU computers after Anniversary update then you probably have Hyper-V on Windows 10 Home). There are a few workarounds until the Docker team addresses this issue.
You could use Docker from inside WSL (Windows Subsystem for Linux). Microsoft claims WSL accesses everything directly without Hyper-V so this should be theoretically at the same speed. Of course you can't use your GPU at all because of limitations with GPU passthrough on WSL, which you can ask to be resolved here.
You can also use Docker Toolbox as the other answer stated with Virtualbox, but this will be inherently much slower as you're virtualizing a container inside a virtualized container. You should be able to theoretically get GPU support through this, as well as other features e.g. GUI that you wouldn't be able to with WSL.
To answer the "usefulness" portion of the question:
It's also useful if you run code on a server, but need to develop/debug/update it. You want to test it locally, but to make sure the environment in which it executes is the same (to avoid unexpected, environment specific behavior), you use Docker both locally and on the server. In such a case, even though it's slow, I'll spin up a VM on my W10 Home laptop and run Docker in it.
The greatest feature of the Windows 10 Home May 2020 Update is Windows Subsystem for Linus 2. You can docker in it without the need for a complete virtual machine as in Virtual Box.
Install Docker Desktop that it will automatically indentify WSL2.
I have installed a VMWare 7.1 workstation for ubuntu 12.01. After using vmware for a month the folder contains too many of .vmdk files. Its costing the partition memory low.
1) How to free the memory that occupied by the vmware temporary memory.
2) What can i do to the .VMDK files - too many files are there is in the source path.
1)Go to the snapshot manager and delete the old snap shot. It will give some free memory space
2)Go to the Setting windows and choose snapshot and set the snap shot setting when power off.
I started on Ubuntu and have had the first considerable error. I'm looking for help.
I have an HP Pavilion dv6 i7. I had installed windows 7 and I decided to also install Ubuntu using a USB.
My first attempt was to install Ubuntu 11.10 following the instructions of the official Ubuntu website. When loading the pendrive, my PC stucks at the main menu of ubuntu, so after searching, I found could be due to a problem with my AMD Radeon graphic card (or not), but I decided to change.
Then I used Ubuntu 10.4. This could happen from the start menu i get into Ubuntu live. There I decided to install it because I liked it and I need to develope with Google TV (in windows is not posible).
And I fail in the partitions section. I tried to follow the instructions on this page:
http://hadesbego.blogspot.com/2010/08/instalando-linux-en-hp-pavilion-dv6.html
but there were things that changed a bit so I improvised. I took the windows partition of 700000MB and went to 600000Mb leaving 100GB free to install Linux there. The error was to set it to ext3 (it was ntfs). I thought the new 100gb partition will be set to ext3, and windows partition will stuck at ntfs system, but not.
Total I ran out to boot windows, and above I can not install ubuntu on the 100GB free.
Someone thinks I can help. Is there any easy way to convert back to ntfs windows and not lose data?
Thank you very much.
You should be able to hit F11 when the machine is booting up and go to the HP recovery application. This should let you reset to factory default.
You should definitely be able to install Ubuntu on the new 100GB partition as well. Just make sure you choose the right partition to install it on.
You will need to recover using recovery CD/DVD's. You must have been using the install gparted utility in Linux to "re-partition" your drive. You scrubbed some boot files.
If you successfully recover using the recovery media you can use Disk Management in Win 7 to shrink or extend your volume. In your case you would shrink it down 100Gb's and then when installing Linux gparted will see that available 100 GB and install there while Windows will still run.
Also, you should probably be running ext4 fs, not ext3. you would only want ext3 for compatibility reasons.