-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Cannot start test containers - No filesystems present in Docker (on Mac) Version 1.13.0 (15072) #273
Comments
Hi @robshep
Regardless, though, the disk space check should be best-efforts and in my view should not abort even when the |
Thanks Peter, My
as opposed to your aufs. Upon installation of 1.13.0 it wouldn't start so I had to reset it via the docker whale menu to factory defaults. Maybe it chose a new incoming default. I certainly have mounted filesystems:
I've just tried with Relaxing the hard requirement of some df output would be ok with me ;) |
…ws no available volumes (see #273). While the cause is not known, and Docker may yet fail, relaxing this constraint at least lets Docker try without aborting prematurely.
Thanks Richard. Just to complete the investigation... In the Daemon > advanced setting of the docker menu I switched to aufs as follows, and the df command works as expected. { |
…ws no available volumes (see #273). While the cause is not known, and Docker may yet fail, relaxing this constraint at least lets Docker try without aborting prematurely.
…ws no available volumes (see #273). While the cause is not known, and Docker may yet fail, relaxing this constraint at least lets Docker try without aborting prematurely. Use functional operation to compare disk space if not null
I just upgraded to Version 1.13.0 (15072)
I cannot start my test containers:
Running df in the alpine 3.2 image, I have found that, on my setup at least, there are no filesystems mounted as shown by
df
There doesn't seem to be a reasonable scope for a workaround. TestContainers needs to run
df -P
to workout the available diskspace.Stuck for the moment.....
The text was updated successfully, but these errors were encountered: