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

Fix issue where small tmpfs on /tmp fills easily. #47

Merged
merged 2 commits into from
Jan 4, 2018

Conversation

daithiocrualaoich
Copy link
Member

Change to not have a separate mount for /tmp. It's okay to use the root disk image in this case.

Copy link
Member

@passy passy left a comment

Choose a reason for hiding this comment

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

Wouldn't increasing the tmpfs be a better solution? Where does the original size come from? Or is this to preserve RAM?

@daithiocrualaoich
Copy link
Member Author

@passy Some of the container tools use /tmp for storage, e.g. docker2aci puts the output image in /tmp while it is being created. Since some of the containers can get pretty large, in the GBs for some of the bigger ones, this exhausts the 1GB size set for the tmpfs.

Don't really want to set a tmpfs with 4-8GB either.

@daithiocrualaoich
Copy link
Member Author

Will merge for now. Want to come back at some point and look at using xhyve directly instead of the corectl/Hyperkit wrapper daemon. This will allow more direct configuration of the CoreOS instance for this and other values.

@daithiocrualaoich daithiocrualaoich merged commit 86d2cae into master Jan 4, 2018
@daithiocrualaoich daithiocrualaoich deleted the tmp_directory_fix branch January 4, 2018 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants