Skip to content

Set default to overlay from storage.conf#870

Merged
rhatdan merged 1 commit intocontainers:masterfrom
rhatdan:overlay
Apr 3, 2021
Merged

Set default to overlay from storage.conf#870
rhatdan merged 1 commit intocontainers:masterfrom
rhatdan:overlay

Conversation

@rhatdan
Copy link
Copy Markdown
Member

@rhatdan rhatdan commented Apr 2, 2021

If users do not set the storage driver in their storage.conf, tools that
use containers/storage will print a warning. Since we recommend that
users should use "overlay" driver by default, we should set the settings
in our default storage.conf. This ways distros that just grab the
storage.conf in the storage library will work without the warning.

Signed-off-by: Daniel J Walsh dwalsh@redhat.com

If users do not set the storage driver in their storage.conf, tools that
use containers/storage will print a warning. Since we recommend that
users should use "overlay" driver by default, we should set the settings
in our default storage.conf. This ways distros that just grab the
storage.conf in the storage library will work without the warning.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
@rhatdan
Copy link
Copy Markdown
Member Author

rhatdan commented Apr 2, 2021

@nalind PTAL

@nalind
Copy link
Copy Markdown
Member

nalind commented Apr 2, 2021

LGTM

@TomSweeneyRedHat
Copy link
Copy Markdown
Member

Change LGTM
but tests aren't hip

@rhatdan rhatdan merged commit 6d85274 into containers:master Apr 3, 2021
@TomSweeneyRedHat
Copy link
Copy Markdown
Member

@ypu @ddarrah we may need to adjust some of the RHEL tests for this. Thoughts?

@ypu
Copy link
Copy Markdown

ypu commented Apr 19, 2021

Hi @TomSweeneyRedHat As overlayfs is the default storage driver from code this should be not influence of testing in rhel a lot for now. But it is good to have a record for such change in upstream from QE side. Thanks a lot for your reminding.

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

Successfully merging this pull request may close these issues.

4 participants