Cloud Posse distribution of awesome apps.
This project is part of our comprehensive "SweetOps" approach towards DevOps.
It's 100% Open Source and licensed under the APACHE2.
Use this repo to easily install releases of popular Open Source apps. We provide a few ways to use it.
- Make Based Installer. This installer works regardless of your OS and distribution. It downloads packages directly from their GitHub source repos and installs them to your
- Alpine Linux Packages. Use our Alpine repository to install prebuilt packages that use the original source binary (where possible) from the maintainers' official GitHub repo releases.
- Docker Image. Use our docker image as a base-image or as part of a multi-stage docker build. The docker image always distributes the latest linux binaries for
See examples below for usage.
Is one of our packages out of date?
Open up an issue or submit a PR (preferred). We'll review quickly!
Alpine Repository (recommended)
A public Alpine repository is provided by Cloud Posse. The repository is hosted on Amazon S3 and fronted by CloudFlare's CDN with end-to-end TLS. This ensures insane availability with DDoS mitigation and low-cost hosting. Using this alpine repository is ultimately more reliable than depending on GitHub for availability and provides an easier way to manage dependencies pinned at multiple versions.
The repository itself is managed using
alpinist, which takes care of the heavy lifting of building repository indexes. You can self-host your own Alpine repository using this strategy.
Configure the alpine repository:
The Easy Way
We provide a bootstrap script to configure the alpine repository for your version of alpine.
curl -sSL https://apk.cloudposse.com/install.sh | sh
curl to run:
Add the following to your
Dockerfile near the top.
# Install the cloudposse alpine repository ADD https://firstname.lastname@example.org /etc/apk/keys/ RUN echo "@cloudposse https://apk.cloudposse.com/3.11/vendor" >> /etc/apk/repositories
NOTE: we support alpine
3.11 packages at this time
Installing Alpine Packages
When adding packages, we recommend using
apk add --update $package to update the repository index before installing packages.
Simply install any package as normal:
apk add gomplate
But we recommend that you use version pinning:
apk add gomplate==3.0.0-r0
And maybe even repository pinning, so you know that you get our versions:
apk add gomplate@cloudposse==3.0.0-r0
Makefile interface works on OSX and Linux. It's a great way to distribute binaries in an OS-agnostic way which does not depend on a package manager (e.g. no
This method is ideal for local development environments (which is how we use it) where you need the dependencies installed natively for your OS/architecture, such as installing a package on OSX.
See all available packages:
make -C install help
make -C install all
Install specific packages:
make -C install aws-vault chamber
Install to a specific folder:
make -C install aws-vault INSTALL_PATH=/usr/bin
Uninstall a specific package
make -C uninstall yq
Docker Multi-stage Build
Add this to a
Dockerfile to install packages using a multi-stage build process:
FROM cloudposse/packages:latest AS packages COPY --from=packages /packages/bin/kubectl /usr/local/bin/
Docker with Git Clone
Or... add this to a
Dockerfile to easily install packages on-demand:
RUN git clone --depth=1 -b master https://github.com/cloudposse/packages.git /packages && \ rm -rf /packages/.git && \ make -C /packages/install kubectl
Sometimes it's necessary to install some binary dependencies when building projects. For example, we frequently
helm to build chart packages.
Here's a stub you can include into a
Makefile to make it easier to install binary dependencies.
export PACKAGES_VERSION ?= master export PACKAGES_PATH ?= packages/ export INSTALL_PATH ?= $(PACKAGES_PATH)/bin ## Install packages packages/install: @if [ ! -d $(PACKAGES_PATH) ]; then \ echo "Installing packages $(PACKAGES_VERSION)..."; \ rm -rf $(PACKAGES_PATH); \ git clone --depth=1 -b $(PACKAGES_VERSION) https://github.com/cloudposse/packages.git $(PACKAGES_PATH); \ rm -rf $(PACKAGES_PATH)/.git; \ fi ## Install package (e.g. helm, helmfile, kubectl) packages/install/%: packages/install @make -C $(PACKAGES_PATH)/install $(subst packages/install/,,$@) ## Uninstall package (e.g. helm, helmfile, kubectl) packages/uninstall/%: @make -C $(PACKAGES_PATH)/uninstall $(subst packages/uninstall/,,$@)
Contributing Additional Packages
In addition to following the Contributing section, the following steps can be used to add new packages for review (via a PR).
- Clone an existing, similar, package within the vendors directory. Name the new folder with the same name as the binary package being installed.
- At a minimum, update the
Makefileto reflect the binary being installed. Ensure that a test task exist in the package Makefile.
- Test the install and ensure that it downloads and runs as expected (
make -C install <your_package> INSTALL_PATH=/tmp)
- Test the apk build (see below)
- Update the
make init readme/deps readme)
Testing apk builds
To validate that a new package will build into an apk you can use the following steps;
make docker/build/apk/shell make -C vendor/<appname> apk # Some temp build files in the volume mount set user/group to nobody/nobody for apk building. # It is easier to remove them while within the docker container. rm -rf ./tmp/build.* exit
Share the Love
Like this project? Please give it a ★ on our GitHub! (it helps us a lot)
Are you using this project or any of our other projects? Consider leaving a testimonial. =)
Check out these related projects.
- build-harness - Collection of Makefiles to facilitate building Golang projects, Dockerfiles, Helm charts, and more
- geodesic - Geodesic is the fastest way to get up and running with a rock solid, production grade cloud platform built on strictly Open Source tools.
Got a question? We got answers.
DevOps Accelerator for Startups
We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
- Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
- Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
- Site Reliability Engineering. You'll have total visibility into your apps and microservices.
- Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
- GitOps. You'll be able to operate your infrastructure via Pull Requests.
- Training. You'll receive hands-on training so your team can operate what we build.
- Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
- Troubleshooting. You'll get help to triage when things aren't working.
- Code Reviews. You'll receive constructive feedback on Pull Requests.
- Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.
Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.
Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!
Bug Reports & Feature Requests
Please use the issue tracker to report any bugs or file feature requests.
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull Request so that we can review your changes
NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!
Copyright © 2017-2020 Cloud Posse, LLC
See LICENSE for full details.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
All other trademarks referenced herein are the property of their respective owners.
We offer paid support on all of our projects.