Likelihood to Recommend CoreOS rkt is well suited for any development environment where operating systems and hardware are not homogeneous. CoreOS rkt allows us to write code on one machine with the confidence that it will work on any other. This has been immensely helpful as our developers are often switching to the latest and greatest machines and operating systems. CoreOS rkt is less suited for environments that are not Software as a Service. There is often no need to bring the entire developer environment and associated dependencies when delivering a one time product. In these environments CoreOS rkt just adds unneeded overhead.
Read full review As of current, the only artifactory management tool that I would recommend is ProGet. The free version is plentiful in features, supporting all feed types that the paid plans do. The paid plans also add even more capabilities on top of the free plan, such as data retention policies, which helps to minimize storage waste on my server and keep everything clean.
Read full review Pros Running a secure container without messing up with low-level details Very clear and straightforward approach to building a container A way to go for new projects thinking of containers Comprehensive and well-written documentation compatible with UNIX keep it simple way of thinking Read full review The Docker registry feature works great. Compared to Sonatype Nexus 3, I don't need to set up extra ports, as everything just works off the port ProGet itself is running on. Debian feeds support automatic GPG key generation, without me having to create or manage them myself. This is another spot where ProGet is better than Nexus, as you have to manually create and specify a key with Nexus, while ProGet simply handles it all for you. Read full review Cons Market share, it's often very difficult to find new talent who use CoreOS rkt. Lack of wow features, CoreOS rkt doesn't necessarily offer any immediate advantages over other container solutions. Read full review When running ProGet inside of a Docker container, changes to some settings requires a manual restart of the container (i.e. with 'docker restart x'). Read full review Alternatives Considered Docker, lxc, Ubuntu Snappy, partisan chroot+unshare Reformulating the problem and realizing a container is not necessary when a testing environment with clearly defined behavior.
Read full review Both Sonatype Nexus 3 and ProGet support all the feed types I use, but ProGet simply does them better. The Docker feeds run on the same port as ProGet itself, while Nexus requires additional ports to be set up, which can be a burden when running in Docker. Debian feeds also support GPG key creation without having to manually specify one, again, reducing the burden for me to manually do things, allowing me to set up and distribute my programs even quicker.
Read full review Return on Investment Developers spend less time configuring and more time coding. Less time training developers as CoreOS rkt lets them use whatever hardware and operating system they want. Reduced our IT costs, solutions are containerized using CoreOS rkt meaning they can write one solution with many developers in mind. Read full review I don't need to develop custom solutions for distributing my software, as ProGet does it all for me. ProGet also integrates easily into my CI systems, with a fully-featured API that allows me to upload packages right after building. Read full review ScreenShots