Oh yeah there is a lot you can implement to really get the most out of your architecture via docker and minimize your build times.
One is using BuildKit with BuildX and Docker Build Cache.
BuildX is the one I highly recommend getting familiar with as it’s essentially an extension of BuildKit.
I’m a solutions architect so I was literally building with these tools 15 minutes ago lol. Send any other questions my way if you have any!
Someone doesn’t know how to leverage Docker BuildKit
But this way I can give Apple my money and Google my data in one simple package!
The body is not a perfect thermal insulator so you must note that the liquid in the bladder is constantly losing heat due to dissipation into the surrounding tissues then the environment around the body. The greater the temperature differential between the body and the environment, the faster the rate of transfer. Your body won’t (or at least it’ll try its damndest) to not let that internal temp drop, which will take more and more energy to maintain as the external temp drops.
And quite a few more!
Army, Navy, Air Force academies each have their own D1 rifle programs as well.
Oh! I actually can personally answer this one. I’ve been a competitive air gun and rimfire .22 LR for years and even attended college on a rifle program scholarship at a D1 program (yes! The US has a major collegiate rifle program)
Traveling internationally depended much on where you were going. We competed at the international junior Olympic championships just outside of London one year in the UK. We had to package all ammo and firearms separately, in locked containers which ultimately wasn’t that big a deal. As with flying with firearms in the US, it ultimately comes down to how familiar those such as gate agents and check-in staff are at the airport with their country’s firearm travel laws. Flying out of the US was always easy as they’re used to firearms, but flying back to the US was sometimes a nightmare and we’d get to the airport up to 6 hours before a flight to deal with any BS.
Tried Ubuntu, Drauger OS, Fedora, and Popos. It’s specifically the laptop hardware that’s giving trouble and as far as the drivers go it’s just really a mess because of X11 vs Wayland issues with Nvidia making it all the more difficult.
Heres my current core issue: I need to run nvidia official drivers as the ones provided via open repos don’t support eGPUs/multi-gpu setups. The problem there is nvidia official drivers only support x11, so then I’m forced to used a sunsetting windowing system for my daily driver, which I just can’t bring myself to do.
Okay back that up: I just tried my third time in 5 years to run Linux as a daily driver for software dev work and gaming. I’m on an ASUS ROG Zephyrus M16 2022 and I’ve never been able to fully get Linux working. Here’s my takeaways (and I really wanted Linux to work out fwiw):
But sure proton is great! /s it’s only viable if the damn hardware works in the first place which Linux simply can’t do yet
Yeah! So the first thing that BuildKit provides that greatly improves build time is that it will detect and run the two stages (one, two) in parallel so the wall-clock time for your example is 5s (excluding any overhead). Without BuildKit, these would be built serially resulting in a wall-clock time of 10s (excluding any overhead).
Additionally, BuildKit uses a content-based cache rather than a step-by-step key cache used by classical Docker. This content-based cache is intelligently reused across different builds and even re-ordered instructions. If you were to build then rebuild your example, the sleep steps would be skipped entirely as those steps are fully completed and unchanged in the content-based cache from the previous build. It will detect changes and re-build accordingly.
Lastly, (albiet not a BuildKit feature directly) is to leverage inline build caching for things such as dependencies so they are persisted to your filesystem and mounted during build time such that you don’t have to fetch them constantly. This isn’t really necessary if leveraging BuildKit fully since the content-based cache will also handle the dependencies and only pull if changed. i.e:
RUN --mount=type=cache,target=/root/.cache \ your-build-command