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

Do not validate snapshotter argument if docker is enabled #2800

Merged
merged 1 commit into from
Jan 20, 2021

Conversation

sonicaj
Copy link
Contributor

@sonicaj sonicaj commented Jan 11, 2021

Problem:
While using ZFS on debian and K3s with docker, I am unable to get k3s working as the snapshotter value is being validated and the validation fails.

Solution:
We should not validate snapshotter value if we are using docker as it's a no-op in that case.

Signed-off-by: Waqar Ahmed waqarahmedjoyia@live.com

Types of Changes

Bug Fix

Linked Issues

Related to #2920

Problem:
While using ZFS on debian and K3s with docker, I am unable to get k3s working as the snapshotter value is being validated and the validation fails.

Solution:
We should not validate snapshotter value if we are using docker as it's a no-op in that case.

Signed-off-by: Waqar Ahmed <waqarahmedjoyia@live.com>
@sonicaj sonicaj requested a review from a team as a code owner January 11, 2021 15:42
@brandond
Copy link
Member

Why are you passing the argument at all then?

@sonicaj
Copy link
Contributor Author

sonicaj commented Jan 11, 2021

I am not, it has a default value

@brandond
Copy link
Member

brandond commented Jan 11, 2021

LGTM. This appears to be the same check we're using at
https://github.com/k3s-io/k3s/blob/master/pkg/agent/config/config.go#L479

@brandond brandond self-assigned this Jan 11, 2021
@brandond brandond merged commit 3ea6968 into k3s-io:master Jan 20, 2021
@sonicaj sonicaj deleted the agent-fix branch January 20, 2021 20:44
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.

3 participants