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

give Docker a storage quota of 20Gb #669

Closed
yegor256 opened this issue Dec 4, 2014 · 21 comments
Closed

give Docker a storage quota of 20Gb #669

yegor256 opened this issue Dec 4, 2014 · 21 comments
Labels

Comments

@yegor256
Copy link
Owner

yegor256 commented Dec 4, 2014

No description provided.

@yegor256
Copy link
Owner Author

yegor256 commented Dec 4, 2014

@yegor256
Copy link
Owner Author

yegor256 commented Dec 4, 2014

@yegor256
Copy link
Owner Author

yegor256 commented Dec 4, 2014

we need Docker older than 1.2.0

@yegor256
Copy link
Owner Author

yegor256 commented Dec 4, 2014

this --storage-opt dm.basesize=20G doesn't work in this docker:

$ sudo docker version
Client version: 1.3.1
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): c78088f/1.3.1
OS/Arch (client): linux/amd64
Server version: 1.3.1
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): c78088f/1.3.1

@original-brownbear
Copy link
Contributor

@yegor256 can you close this?, to me it looks like this is long obsolete given we're on docker 1.9.x now.

@original-brownbear
Copy link
Contributor

@yegor256 ping :)

@yegor256
Copy link
Owner Author

@original-brownbear but it's not fixed, right? we don't have 20Gb storage quota now.

@alex-palevsky alex-palevsky mentioned this issue Feb 29, 2016
@original-brownbear
Copy link
Contributor

@yegor256 soory I fear I've misinterpreted this.

My understanding was that Docker 1.3.x broke the setting of a non-default dm.basesize=20G here.

This should be resolved in 1.9+ as far as I could research this.
But thinking about it now, likely you long gave up on setting this setting for the daemon right ? ...
Still I think simply setting this option now and restarting the Docker daemon should put the quote in place.
Maybe give it a try ? ( and in the unlikely case it fails, paste the output of docker info here ?)

@yegor256
Copy link
Owner Author

yegor256 commented Mar 1, 2016

@original-brownbear I didn't understand what do you want me to do

@original-brownbear
Copy link
Contributor

@yegor256 sorry, just wanted you to try running the Docker daemon with the --storage-opt dm.basesize=20G flag :)

@yegor256
Copy link
Owner Author

yegor256 commented Mar 2, 2016

@original-brownbear well, I run it like this:

$ sudo service docker start

I think it's better to provide all flag/params from rultor, instead of configuring Docker on the server. Since there are other project, which are using Docker. They may not need these settings.

@original-brownbear
Copy link
Contributor

@yegor256 bad news then I fear, storage quote can only be set globally for the Docker daemon at this point. Per container settings are being implemented here moby/moby#3804. If we only want this for some containers coming from Rultor we'll have to wait :(

@yegor256
Copy link
Owner Author

yegor256 commented Mar 2, 2016

@original-brownbear let's wait

@original-brownbear
Copy link
Contributor

@alex-palevsky this is a bug.

@original-brownbear
Copy link
Contributor

@alex-palevsky this is postponed.

@alex-palevsky
Copy link
Contributor

@alex-palevsky this is a bug.

@original-brownbear tag bug added to this issue

@alex-palevsky alex-palevsky added this to the 2.0 milestone Mar 2, 2016
@alex-palevsky
Copy link
Contributor

@yegor256 attached this issue to milestone "2.0" (let me know if this is wrong)

@alex-palevsky
Copy link
Contributor

@yegor256 thanks for reporting! I topped your account for 15 mins, transaction 000-59cec294

@alex-palevsky
Copy link
Contributor

@alex-palevsky this is postponed.

@original-brownbear OK, I put "postponed" label here

@alex-palevsky
Copy link
Contributor

@alex-palevsky this is postponed.

@original-brownbear I will assign somebody else to this issue

@yegor256 yegor256 removed this from the 2.0 milestone Nov 7, 2022
@yegor256
Copy link
Owner Author

@original-brownbear we won't fix this, since we move to EC2

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

No branches or pull requests

3 participants