docker-cleanup | DEPRECATED Automatic Docker image , container | Continuous Deployment library

by meltwater Shell Version: 1.8.0 License: MIT

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

kandi X-RAY | docker-cleanup Summary

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

This image will periodically clean up exited containers and remove images and volumes that aren't in use by a running container. Based on tutumcloud/image-cleanup and chadoe/docker-cleanup-volumes with some small fixes. Normally any Docker containers that exit are still kept on disk until docker rm -v is used to clean them up. Similarly any images that aren't used any more are kept around. For a cluster node that see lots of containers start and stop, large amounts of exited containers and old image versions can fill up the disk. A Jenkins build slave has the same issues, but can also suffer from SNAPSHOT images being continuously rebuilt and causing untagged images to be left around.

Support

Quality

Security

License

Reuse

Support

docker-cleanup has a low active ecosystem.

It has 584 star(s) with 115 fork(s). There are 48 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 23 have been closed. On average issues are closed in 387 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of docker-cleanup is 1.8.0

Quality

docker-cleanup has 0 bugs and 0 code smells.

Security

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

docker-cleanup code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

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

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

Reuse

docker-cleanup releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

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

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

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

Vulnerabilities

No vulnerabilities reported

Install docker-cleanup

You can download it from GitHub.

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: