This is usually a challenge that any developer has to take care of when building an AI agent. In fact, managing the context is one of the hardest problems when working with AI agents and there are many companies like SuperMemory, Mem0 which have invested both resources and time to solve this problem. - Source: dev.to / about 1 month ago

Memory. I use Supermemory for this. Before, Pipa loaded context files and knew to update them. A memory tool adds teammate-like recall: goals, preferences, latest business state, and small details that should carry across runs. Good memory tools also know how to supersede and delete memories, which matters once the agent has more autonomy. - Source: dev.to / 3 months ago

We wire everything up with Vision Agents as the voice agent framework, Stream for WebRTC audio and video, OpenAI Realtime for speech in and speech out, Anam so the agent shows up as a face on the video, and Supermemory so answers come from search over your uploaded documents instead of guesswork. The code stays small and most of the behavior lives in one registered function that asks the memory store for relevant... - Source: dev.to / 4 months ago

My friends and I are working on https://supermemory.ai, an AI second brain to help you remember content from saved webpages and notes. - Source: Hacker News / about 2 years ago

Modern Docker releases use BuildKit, an efficient builder developed by Docker, whereas Podman uses Red Hat's Buildah. However, both solutions output OCI-compliant images, so there's no practical difference between the two for standard build workflows. - Source: dev.to / about 1 year ago

I suspect that the GP was really asking "why not use a different tool", like buildah , buildpacks , nix ,. - Source: Hacker News / over 1 year ago

Buildah specializes in building OCI-compliant container images, offering a more granular and secure approach to image creation compared to traditional Dockerfile builds. - Source: dev.to / over 1 year ago

Lockdown your Dockerized build environments --- Because privileged mode is insecure, you should restrict your CI/CD environments to known users and projects. If this isn't feasible, then instead of using Docker, you could try using a standalone image builder like Buildah to eliminate the risk. Alternatively, configuring rootless Docker-in-Docker can mitigate some --- but not all --- of the security concerns... - Source: dev.to / over 2 years ago

In my experience, not using docker to build docker images is a good idea. E.g. buildah[0] with chroot isolation can build images in a GitLab pipeline, where docker would fail. It can still use the same Dockerfile though. If you want to get rid of your Dockerfiles anyway, nix can also build docker images[1] with all the added benefits of nix (reproducibility, efficient building and caching, automatic layering,... - Source: Hacker News / almost 3 years ago