buildx
virtual-environments
buildx | virtual-environments | |
---|---|---|
28 | 54 | |
3,230 | 6,399 | |
1.5% | - | |
9.6 | 9.8 | |
7 days ago | over 1 year ago | |
Go | PowerShell | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
buildx
-
BuildKit in depth: Docker's build engine explained
This is great! I’ve been waiting a long time for this and it seems like more debug features are in the pipeline too: https://github.com/docker/buildx/issues/1104
Docs: https://docs.docker.com/engine/reference/commandline/buildx_...
-
Nx + NextJS + Docker - The Nx way: Creating the NextJS application
Container engine: Docker v23.0.4 | Buildx v0.10.4
- Using Docker Buildx to Create Cross-Platform Docker Images for Seamless Compatibility
-
Cross-platform container images with buildx and colima
ARCH=amd64 # change to 'arm64' for M1 VERSION=v0.10.4 curl -LO https://github.com/docker/buildx/releases/download/${VERSION}/buildx-${VERSION}.darwin-${ARCH} mkdir -p ~/.docker/cli-plugins mv buildx-${VERSION}.darwin-${ARCH} ~/.docker/cli-plugins/docker-buildx chmod +x ~/.docker/cli-plugins/docker-buildx docker buildx version # verify installation
-
Help Downloading Buildx on Play-with-Docker Instance
wget -O /tmp/docker/cli-plugins/docker-buildx https://github.com/docker/buildx/releases/tag/v0.10.4/buildx-v0.10.4.linux-amd64
-
docker-ce upgrade broke my builds
Your particular one looks somewhat like https://github.com/docker/buildx/issues/1595.
-
One Dockerfile is all it takes, falling in love with bake
Now, we have examples of the actual definitions for a single application’s docker container. Notice that we set the contexts key here which references the dependency targets we just defined. You can basically think of this like the depends_on block if you’ve used Terraform before. The args key let’s us populate the ARG variables in the Dockerfile. This is what is ultimately different between each of the containers. In the future, the buildx team might support using for_each loops like in Terraform but for now each block will have a bit of duplication.
-
Optimize your docker containers
Now as bonus we i will add how to use this techniques to build a multi arch build container. Maybe you have the same application but you need to run it in arm or riscv architecture. For this we can use the buildx plugin from docker https://github.com/docker/buildx.
-
Pushing Cutom Images to Docker Hub using GitHub Actions
Third step is docker/setup-buildx-action configures buildx, which is a Docker CLI plugin that provides enhanced build capabilities.
- How to build multi-architecture Docker images?
virtual-environments
-
Deploy to Google AppEngine with GitHubActions
This action runs using Node 16. If you are using self-hosted GitHub Actions runners, you must use runner version 2.285.0 or newer.
-
Ensuring Your E2E Tests Run On Every Code Push
This is the OS and version used for the virtual environment in which run our tests. I recommend always using a specific version, such as the latest stable version, rather than latest, which is risky because you may then suddenly start to see test failures caused by a version update that has nothing to do with your tests. See virtual-enviroments for the latest stable version.
-
How would you suggest running unit tests within containers in a CI AKS based considering docker.sock isn’t available anymore?
This, I setup Azure DevOps pipeline that clones this: https://github.com/actions/virtual-environments Runs it in Linux servers, copies VHD into Storage Account, creates an image from it and makes it new image for Azure Scale Set. Runs every Monday Morning on timer.
-
Ask HN: How are you dealing with the M1/ARM migration?
I'm in a similar boat - love the performance/battery of my M1 MacBook Air, but the ecosystem is just too messy at the moment for me. I have a few tools I need to use that haven't yet been making official Apple Silicon releases due to GitHub actions not supporting Apple Silicon fully yet. The workaround involves maintaining two versions of homebrew, one for ARM and one for x86-64, and then being super careful to make sure you don't forget if you're working in an environment that's ARM and one that's X86. It's too much of a pain to keep straight for me (I admit it - I lack patience and am forgetful, so this is a bit of a "me" problem versus a tech problem).
My solution was to give up using my M1 mac for development work. It sits on a desk as my email and music machine, and I moved all my dev work to an x86 Linux laptop. I'll probably drift back to my mac if the tools I need start to properly support Apple Silicon without hacky workarounds, but until GitHub actions supports it and people start doing official releases through that mechanism, I'm kinda stuck.
It is interesting how much impact GitHub has had by not having Apple Silicon support. Just look at the ticket for this issue to see the surprisingly long list of projects that are affected. (See: https://github.com/actions/virtual-environments/issues/2187)
-
Struggling to setup GithubAction with a .NET 4 app build
https://github.com/actions/virtual-environments/issues you can always request additional software to added to GitHub's machines, costs nothing to ask.
-
Any tool that can help me convert Azure ADO Pipelines to GitHub Actions YAML?
I'm not disputing your claim that it could be true as I say, it makes sense, there is even some evidence they are getting ready for feature parity as I said in my comment with the hosted agent builds but I am arguing the point with my "what aboutism" as it isn't clear.
-
Czkawka 4.1.0 - Fast duplicate finder, with finding invalid extensions, faster previews, builtin icons and a lot of fixes
Also Ubuntu 22.04 is not currently available on Github so I can't use CI for now - https://github.com/actions/virtual-environments/issues/5428
-
Emacs 28.1's been cut
As for M1 support, I’m still waiting for GitHub to add M1-based GitHub Actions runners (issue).
-
Getting started with GitHub Actions and workflows
GitHub provides hosted runners which can run your workflow in different virtual environments. The "ubuntu-latest" environment already contains a recent version of Node.js which is ideal for testing JavaScript applications.
-
AzurePipeline failing due to: The reference assemblies for .NETFramework,Version=v4.6.1 were not found
As mentioned in this GitHub issue, the issue seems to affect only windows-2022 image. You can use the following script to install .NETFramework 4.6.1 to the agent.
What are some alternatives?
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
action-gh-release - 📦 :octocat: GitHub Action for creating GitHub Releases
ghaction-docker-meta - GitHub Action to extract metadata (tags, labels) for Docker [Moved to: https://github.com/docker/metadata-action]
act - Run your GitHub Actions locally 🚀
aws-graviton-getting-started - Helping developers to use AWS Graviton2 and Graviton3 processors which power the 6th and 7th generation of Amazon EC2 instances (C6g[d], M6g[d], R6g[d], T4g, X2gd, C6gn, I4g, Im4gn, Is4gen, G5g, C7g[d][n], M7g[d], R7g[d]).
widevine-l3-guesser
crates.io-index - Registry index for crates.io
runner - The Runner for GitHub Actions :rocket:
build-push-action - GitHub Action to build and push Docker images with Buildx
SwagLyrics-For-Spotify - 📃 Get lyrics of currently playing Spotify song so you don't sing along with the wrong ones and embarrass yourself later. Very fast.
multi-platform-docker-build - Using BuildKit and TARGETPLATFORM for cross-platform Dockerfiles
UTM - Virtual machines for iOS and macOS