

I know you just mastered object permanence, please move on to reading comprehension soon!
I know you just mastered object permanence, please move on to reading comprehension soon!
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
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
Not even going to buy him dinner first?
It was! I highly recommend that anyone who can, make plans to visit Aruba some day, it’s incredible and the people are wonderful!
A few more from the evening.
Context: https://lemmy.world/post/29732823
I’m also on brave and had to wade through this same issue. Happy to help! Enjoy the mic and awesome setup!
First off, beautiful hardware! Secondly, based on what you’ve said you’ve already tried, you’ve probably run through most of what I’d recommend to troubleshoot this. I don’t experience this issue with my Volt 176 but doing some searching I found a thread that it could be Chrome related? Worth a shot
On Chrome URL
type “chrome://flags/”
Goto > “Allow WebRTC to adjust the input volume” = DISABLE (set to disable)
What mic do you have? Are you going through any intermediate hardware? Ie a Volt device to input XLR mic? Have you disabled “allow applications to take exclusive control of this device”? You will need to go through the “Additional sound settings” option of the windows 11 control panel to access the OG sound settings UI. that will have what you need.
Oh absolutely. I’ve got two Nvidia Jetsons and honestly they’re perfect for running dedicated workloads or automating training runs. I’d love for MB manufacturers to start tossing a soldered NPU/TPU on the board and call it a day
Okay perfect, just wanted to check.
Next I’d say check your venv to verify the pandoc binary is indeed there:
find $VIRTUAL_ENV -name pandoc
If it’s not there, you should be able to install it by entering a python shell from your venv and do:
import pypandoc
pypandoc.download_pandoc()
Hopefully that’s able to resolve it for ya. Venv should be at the front of your path so it should prefer bins from there.
Did you activate your virtual python env with ‘source .venv/bin/activate’? You must do that in each new shell unless you add some config to your shell profile config to have it detect the presence of a python venv.
Yeah, I desire buying hardware without AI, or any other manufacturer bloatware.
Just switched to Fedora Kinoite and I’m loving the immutability of the OS. Oh bad update? lol rollback and golden. Can’t do that shit with each bloatware force push from MS