Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Make titus mount use new patchset #189

Merged
merged 1 commit into from
Oct 16, 2018
Merged

Make titus mount use new patchset #189

merged 1 commit into from
Oct 16, 2018

Conversation

sargun
Copy link
Contributor

@sargun sargun commented Oct 15, 2018

Description of the Change

This uses this patched kernel:
Netflix-Skunkworks/linux@26d791f

@codecov
Copy link

codecov bot commented Oct 15, 2018

Codecov Report

Merging #189 into master will decrease coverage by 0.1%.
The diff coverage is 57.14%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #189      +/-   ##
==========================================
- Coverage   31.54%   31.43%   -0.11%     
==========================================
  Files          66       66              
  Lines        8407     8401       -6     
==========================================
- Hits         2652     2641      -11     
- Misses       5435     5439       +4     
- Partials      320      321       +1
Impacted Files Coverage Δ
executor/runtime/docker/docker.go 50.18% <57.14%> (-0.74%) ⬇️

@sargun sargun merged commit 60561ec into master Oct 16, 2018
@sargun sargun deleted the fix-efs-mount branch October 16, 2018 00:45
@@ -1405,7 +1400,7 @@ const (
)

func (r *DockerRuntime) setupEFSMounts(parentCtx context.Context, c *runtimeTypes.Container, rootFile *os.File, cred *ucred, efsMountInfos []efsMountInfo) error {
baseMountOptions := []string{"nofsc,nosharecache,vers=4"}
baseMountOptions := []string{"vers=4.1,nosharecache,rsize=1048576,wsize=1048576,timeo=600,retrans=2,noresvport"}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason for the other new mount options?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants