8

Containerd is a daemon for running containers. The Docker blog has a nice write up explaining how this fits into Docker. While containerd is used in Docker, it can also be used as a daemon for other container solutions. Containerd requires runc in order to function. runc as defined by the project is a "CLI tool for spawning and running containers ...


5

Considering your first paragraph, the organization you're describing is a highly siloed org, which is exactly what a DevOps organization tend to avoid. Considering this challenge, within DevOps there is a requirement to define and document all the components that constitute the various technology stacks within an IT environment. Traditionally this ...


4

One of the advantages of using Docker would be that you can easily run tests with different versions of the (DB) apps, which could be quite difficult with Homebrew (some apps don't easily support multiple versions installed on the same system).


3

Any organization that needs the level of control you've specified is essentially forced into the preapproval process ("walled garden"). It's a pain for developers, but it's a necessary process to keep the company safe. I've even heard of companies with programs that scan all their workstations regularly to find and remove unapproved software. It's worth ...


3

One of the cons of Homebrew for the use of testing your DB stuff is how tightly coupled the DB is to your local environment. You'll inevitably end up needing to manage the details of what services are running, and possibly needing to manage the versions of multiple installations. This can get complex if you need to install software that needs different ...


2

There are enterprise tools that manage these opensource dependencies namely Jfrog Artifactory with the Xray feature and Inedo ProGet with features for license filtering and vulnerability scanning. Basically, allows you to restrict or permit download of package so companies can set policies to ensure development isn't breaking rights of use or building ...


2

From https://docs.docker.com/docker-hub/official_repos/ Docker, Inc. sponsors a dedicated team that is responsible for reviewing and publishing all content in the official repositories. This team works in collaboration with upstream software maintainers, security experts, and the broader Docker community. While it is preferable to have upstream software ...


1

You essentially have three threats here: Someone could modify .travis-ci and use that to exfiltrate the unencrypted key material. You could accidentally check-in or publish the decrypted key material as part of your release process. Someone could attempt to attack the encrypted key-material directly; this is very unlikely given modern practice and current ...


Only top voted, non community-wiki answers of a minimum length are eligible