docker-cleanup | Remove Obsolete Docker Containers and Images | Continuous Deployment library

by Grk0 Python Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | docker-cleanup Summary

docker-cleanup is a Python library typically used in Devops, Continuous Deployment, Docker applications. docker-cleanup has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

Remove Obsolete Docker Containers and Images

Support

Quality

Security

License

Reuse

Support

docker-cleanup has a low active ecosystem.

It has 10 star(s) with 3 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

docker-cleanup has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of docker-cleanup is current.

Quality

docker-cleanup has no bugs reported.

Security

docker-cleanup has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

docker-cleanup is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

docker-cleanup releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docker-cleanup

Get all kandi verified functions for this library.

docker-cleanup Key Features

No Key Features are available at this moment for docker-cleanup.

docker-cleanup Examples and Code Snippets

No Code Snippets are available at this moment for docker-cleanup.

Community Discussions

Trending Discussions on docker-cleanup

Docker.dotnet ListImages fails with permission denied on /var/run/docker.sock in Redhat

docker change cgroup driver to systemd

Kubernetes: How to automatically clean up unused images

QUESTION

Docker.dotnet ListImages fails with permission denied on /var/run/docker.sock in Redhat

Asked 2021-Apr-04 at 08:16

Disclaimer: I aware the /var/run/docker.sock issue is way common and there are lots of posts out there on it (although most if not all can be summed up to adding the running user to the docker permissions group). I tried all the those instructions and it still does not help me, in redhat.

I have two containers, one Ubuntu and one running Redhat 7.9. My problem is specifically not being able to run - in the redhat container only - a call to Docker.Dotnet's ListImages (fails with permission denied in /var/run/docker.sock). In the beginning, I was not able to issue any docker command without prefixing it with sudo. I then added the running user to the docker permissions group, and can issue docker commands without sudo. But Docker.Dotnet ListImages (which is simply a wrapper to docker api's images/json endpoint) still fails with the permission denied error on docker.sock. I tried all recommended here, to no avail.

I thought perhaps I should add the User=root (although this is not present in my Ubuntu service file, and therefore does not make much sense). I then realized that the ubuntu and redhat docker service files differ considerably.

Ubuntu:

...

ANSWER

Answered 2021-Apr-04 at 08:16

At the end... my problem was that in my Redhat installation, as opposed to my Ubuntu, we had SELinux enabled.

Disabling it finally had curl --unix-socket /run/docker.sock http://docker/images/json working from within my composer containers.

To disable Selinux: edit (you may need to impersonate as root using sudo su root) file /etc/selinux/config - replace SELINUX=enforcing with SELINUX=disabled

Restart the linux server and that's it.

Remark: This may obviously not be an acceptable solution in a production environment. If this is your case, you will need to properly configure SELinux permissions settings. I was simply assigned a task to identify why this problem was happening in one of our dev machines, so disabling it suffices my needs for now.

Source https://stackoverflow.com/questions/66743192

QUESTION

docker change cgroup driver to systemd

Asked 2020-Mar-11 at 06:22

I want to docker to start with systemd cgroup driver. for some reason it using only cgroupfs on my centos 7 server.

here is startup config file.

...

ANSWER

Answered 2017-May-09 at 03:59

Since I have two configuration file I need to add the entry in the second config file also -- /etc/systemd/system/docker.service.d/docker-thinpool.conf:

Source https://stackoverflow.com/questions/43794169

QUESTION

Kubernetes: How to automatically clean up unused images

Asked 2019-Oct-28 at 20:09

Due to some internal issues, we need to remove unused images as soon as they become unused.
I do know it's possible to use Garbage collection but it doesn't offer strict policy as we need. I've come across this solution but

it's deprecated
it also removes containers and possible mounted volumes

I was thinking about setting a cron job directly over the nodes to run docker prune but I hope there is a better way

No idea if it makes a difference but we are using AKS

...

ANSWER

Answered 2019-Oct-28 at 20:09

This doesn't really accomplish much since things will be re-downloaded if they are requested again. But if you insist on a silly thing, best bet is a DaemonSet that runs with the host docker control socket hostPath-mounted in and runs docker system prune as you mentioned. You can't use a cron job so you need to write the loop yourself, probably just bash -c 'while true; do docker system prune && sleep 3600; done' or something.

Source https://stackoverflow.com/questions/58596782

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install docker-cleanup

You can download it from GitHub.
You can use docker-cleanup like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: