# mount Published articles for mount. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions DevFeed: [Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions]() Original publisher: [Read original article]() Author: Nispriha Jagan; Neeraj Krishna Gopalakrishna Published: 2026-09-16T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [mount](), [Filesystems](), [chmod](), [Unix]() Tags: [chmod](), [container](), [containers](), [filesystem](), [hardening](), [kubernetes](), [linux](), [mount](), [permissions](), [storage](), [volume](), [volumes]() ### AI overview Kubernetes v1.37 adds bind mount options and emptyDir permission modes to strengthen storage security. The article explains how noexec, nosuid, nodev, Unix permissions, and the sticky bit can help enforce security policies on writable volumes. ### Source excerpt Kubernetes v1.37 brings important storage security features: emptyDir permission modes and bind mount options. They help application programmers and security professionals implement rigorous security policies, for example, prohibiting deletion of files across containers or execution of arbitrary binaries from writable volumes, directly in Kubernetes without any complicated circumvention. Linux storage and permission fundamentals Before diving into the new Kubernetes features, let us briefly review the low-level Linux security mechanisms that make them possible. Bind mount flags When Linux mounts or remounts a directory, Virtual File System (VFS) flags control what actions are permitted on that filesystem: noexec: Do not permit direct execution of any binaries on the mounted filesystem. nosuid: Do not allow set-user-identifier or set-group-identifier bits to take effect. nodev: Do not interpret character or block special devices on the file system. Directory permissions and the sticky bit Standard Unix permissions regulate access across three scopes: Owner, Group, and Others (e.g., 0755 or 0777). Beyond standard read, write, and execute bits, Linux supports the sticky bit (as in mode 01777). When applied to a directory, the sticky bit ensures that a file inside that directory can only be deleted or renamed by the file's owner or root. This is essential for shared writable directories like /tmp. Motivation for the improvements Why does Kubernetes need bind mount options and emptyDir permissions? The primary goal of these features is to increase the security of Kubernetes workloads by allowing security-related bind mount options on volume mounts. By default, volumes are bind-mounted into containers by the container runtime and kubelet without noexec, nosuid, or nodev flags. This default can undermine security. For example, with noexec missing, a compromised process can use any writable volume (emptyDir, PersistentVolume, etc.) to download, chmod +x, and execute arbitra ## Syitren R400 is a portable Bluetooth CD player with a modular, customizable design DevFeed: [Syitren R400 is a portable Bluetooth CD player with a modular, customizable design]() Original publisher: [Read original article]() Author: Ida Torres Published: 2026-09-15T13:20:31Z Content type: opinion Language: en Sources: [Yanko Design]() Topics: [Hardware](), [Bluetooth]() Tags: [2026](), [a-design-award-and-competition](), [audio](), [audio-music-technology-a-design-award-and-competition-cd-player-music-player](), [bluetooth](), [cd-player](), [collection](), [cost](), [design](), [hardware](), [modular](), [mount](), [music](), [music-player](), [portable](), [product](), [technology]() ### AI overview The article presents Syitren's R400 as an entry-level portable Bluetooth CD player designed by ORGDOT Design. Its detachable modular shell supports customization, a desk stand, and an optional wall-mount bracket, while dual-material construction and cable-management details aim to improve everyday use. ### Source excerpt Finally, a CD Player Gen Z Actually Wants to Own It really warms my heart when I see Gen Z and Gen Alpha kids collecting physical media from their favorite artists. These are people who... ## fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound DevFeed: [fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-11T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [container](), [mount](), [Security](), [Process]() Tags: [container](), [container-image](), [kubernetes](), [mount](), [network](), [performance](), [reliability](), [security](), [stateful](), [storage](), [waiting]() ### AI overview This article explains why a stateful pod can remain in ContainerCreating for fifteen minutes when fsGroup triggers a recursive chown across a large network-backed volume. It describes how fsGroupChangePolicy: OnRootMismatch can skip the recursive walk when the volume root group already matches, and discusses the setgid invariant that supports this behavior. ### Source excerpt Pod stuck in ContainerCreating from fsGroup recursive chown: fsGroupChangePolicy: OnRootMismatch, and why the setgid bit on the volume root makes it safe. ## FastAPI frontends and static files served from the CDN DevFeed: [FastAPI frontends and static files served from the CDN]() Original publisher: [Read original article]() Author: Daniel Park Published: 2026-09-10T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [FastAPI](), [Vercel](), [Front end](), [mount]() Tags: [cdn](), [frontend](), [mount](), [tool](), [vercel]() ### AI overview Vercel now promotes FastAPI frontends and static files served through app.frontend() or StaticFiles to the Vercel CDN at build time, allowing matching requests to bypass Vercel Functions. Route precedence is preserved, while dependency-protected frontends and middleware-protected static files remain on the function unless configured otherwise. ### Source excerpt FastAPI frontends and static files, served with app.frontend() or StaticFiles, are now promoted to the Vercel CDN at build time. Requests for those paths are served directly from the CDN, without invoking your Vercel Function. FastAPI evaluates routes in declaration order. A route declared before a StaticFiles mount takes priority over any CDN file at that path. This precedence is preserved. Promoted source directories remain in the function bundle so the app can read from them at runtime. To exclude them and serve only from the CDN, set tool.vercel.fastapi.static.exclude = true in pyproject.toml. Frontends guarded by dependencies are kept on the function as the CDN cannot run dependency checks. Similarly, static files which sit behind middleware are also kept on the function. To override this and always promote to CDN, set tool.vercel.fastapi.static.cdn = true. To opt out of the CDN entirely, set it to false instead. For more information see the Vercel FastAPI documentation. Read more ## Backblaze B2 x Suite Studios: S3 Native File Streaming Turns B2 Cloud Storage Into a High-Performance Drive DevFeed: [Backblaze B2 x Suite Studios: S3 Native File Streaming Turns B2 Cloud Storage Into a High-Performance Drive]() Original publisher: [Read original article]() Author: Dave Simon Published: 2026-09-10T14:04:38Z Content type: article Language: en Sources: [Backblaze Blog | Cloud Storage & Cloud Backup]() Topics: [Amazon S3](), [Cloud](), [Streaming](), [Filesystems](), [mount](), [data](), [migration]() Tags: [architecture](), [automation](), [b2cloud](), [cloud](), [cloud-storage](), [data](), [featured](), [featured-cloud-storage](), [media](), [media-workflow](), [migration](), [mount](), [nas](), [object-storage](), [s3](), [storage](), [streaming]() ### AI overview Backblaze B2 integrates with Suite Studios' S3 Native File Streaming to provide drive-like, high-performance access to cloud-stored data. Teams can mount B2 buckets, stream only the file portions applications need, and use standard S3-compatible objects without duplicating or relocating datasets. The integration supports media production and other workflows involving large cloud datasets. ### Source excerpt Backblaze B2 now integrates with Suite Studios S3 Native File Streaming, giving teams high-performance, drive-like access to cloud data. Work directly with standard S3-compatible objects across media, scientific, geospatial, and engineering workflows without duplicating datasets or creating new storage silos. The post Backblaze B2 x Suite Studios: S3 Native File Streaming Turns B2 Cloud Storage Into a High-Performance Drive appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Rootless Jailbreak Detection: Updating the Signals, Not the Claim DevFeed: [Rootless Jailbreak Detection: Updating the Signals, Not the Claim]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Jailbreak](), [integrity](), [iOS](), [Filesystems](), [mount](), [Processes]() Tags: [filesystem](), [images](), [integrity](), [ios](), [jailbreak](), [mount](), [process]() ### AI overview Codename One updated its iOS integrity checks to detect current rootless jailbreak layouts. The changes cross-check potentially hooked APIs, inspect mounts and loaded images, and rerun detection when the application returns to the foreground. ### Source excerpt Codename One's iOS integrity checks now detect current rootless jailbreak layouts, cross-check hooked APIs, inspect mounts and loaded images, and rerun on foreground entry. ## Faster Appwrite Sites deployments powered by SquashFS DevFeed: [Faster Appwrite Sites deployments powered by SquashFS]() Original publisher: [Read original article]() Author: Luke B. Silver Published: 2026-08-12T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Deployment](), [mount](), [Cloud]() Tags: [announcements](), [cloud](), [deployment](), [filesystem](), [mount](), [work]() ### AI overview Appwrite is moving new Sites and Functions deployments on Appwrite Cloud to SquashFS. The compressed, read-only filesystem is mounted directly instead of being fully extracted, reducing cold-start work and improving startup predictability, especially for larger Sites. ### Source excerpt Appwrite Sites now packages new deployments with SquashFS, removing archive extraction and cutting the format-dependent cold-start path by up to 51% on larger sites. ## From a Large Allowlist to Three Denials: Permissions for a Coding Agent DevFeed: [From a Large Allowlist to Three Denials: Permissions for a Coding Agent]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-11T07:00:00Z Content type: opinion Language: en Sources: [Philipp Lehmann]() Topics: [coding](), [Bash](), [Linux](), [Authorization](), [Kernel](), [mount](), [Network](), [Command-line interface]() Tags: [agent](), [agents](), [coding](), [command-line](), [curl](), [kernel](), [linux](), [mount](), [network](), [permissions](), [sandboxing](), [security](), [shell]() ### AI overview The article argues that command allowlists are a poor security boundary for coding agents because the required command set continually expands and command names do not constrain effects. It proposes enforcing limits at the kernel level with Linux namespaces, a read-only root filesystem, scoped writable mounts, and dropped capabilities, allowing a shell to run while restricting its blast radius. ### Source excerpt bwrap --unshare-net --cap-drop ALL instead of a command allowlist: sandboxing a coding agent's shell so rm -rf and curl cannot leave the workspace. ## Serverless ICYMI Q2 2026 DevFeed: [Serverless ICYMI Q2 2026]() Original publisher: [Read original article]() Author: Julian Wood Published: 2026-07-20T16:40:00Z Content type: article Language: en Sources: [AWS Compute Blog]() Topics: [Serverless](), [Amazon Web Services](), [AWS Lambda](), [Firecracker](), [Amazon S3](), [Filesystems](), [Linux](), [virtualization](), [mount](), [Latency]() Tags: [2026](), [amazon-eventbridge](), [amazon-s3](), [amazon-simple-storage-service-s3](), [aws](), [aws-lambda](), [aws-step-functions](), [ci-cd](), [firecracker](), [latency](), [linux](), [mount](), [serverless](), [virtualization]() ### AI overview A Q2 2026 recap of AWS serverless launches and resources, focusing on AWS Lambda MicroVMs and Amazon S3 Files integration with Lambda. ### Source excerpt In this 33rd quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q2 2026 that you might have missed. Stay current with the latest serverless innovations that can improve your applications. In case you missed our last ICYMI, read about what happened in Q1 2026. AWS Lambda MicroVMs AWS Lambda [...] ## Vercel Sandbox now supports FUSE-based filesystems DevFeed: [Vercel Sandbox now supports FUSE-based filesystems]() Original publisher: [Read original article]() Author: Brandon Tuttle Published: 2026-07-03T01:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Filesystems](), [mount](), [Amazon S3](), [Network](), [datasets]() Tags: [data](), [datasets](), [driver](), [filesystems](), [mount](), [network](), [object-storage](), [remote](), [s3](), [vercel]() ### AI overview Vercel Sandbox now supports FUSE-based filesystems, allowing remote storage and custom filesystems to be mounted as regular paths inside a running Sandbox. This includes S3 buckets, network filesystems, and other FUSE-compatible drivers, enabling direct access to large datasets without copying them into the Sandbox. ### Source excerpt Vercel Sandbox now supports FUSE, letting you mount remote storage and custom filesystems inside a running Sandbox. Use it to attach S3 buckets, network filesystems, or any other FUSE-compatible driver as a regular path. This makes it possible to stream large datasets directly from object storage, share state across Sandboxes through a common filesystem, or run tools that expect POSIX paths against remote sources without copying data into the Sandbox first. Learn more about remote storage mounts in the documentation. Read more ## Google Drive on Linux: A Fast rclone Mount (and Why Your Thumbnails Are Missing) DevFeed: [Google Drive on Linux: A Fast rclone Mount (and Why Your Thumbnails Are Missing)]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-06-12T10:00:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Google](), [Linux](), [mount](), [Ubuntu](), [systemd](), [Caching](), [xfce](), [OAuth](), [API]() Tags: [browser](), [caching](), [google](), [image](), [linux](), [mount](), [oauth](), [systemd](), [ubuntu](), [xfce]() ### AI overview A tutorial describing a personal setup for mounting Google Drive as a browsable folder on Ubuntu with XFCE using rclone. It covers OAuth authorization, a systemd user service, aggressive caching for faster browsing, and the problem of missing image thumbnails on the mount. ### Source excerpt How I finally got Google Drive working as a fast, normal folder on Linux with rclone -- and fixed the non-obvious problem of missing image thumbnails on FUSE mounts. ## Linux tmpfs for Speed and Temporary Storage DevFeed: [Linux tmpfs for Speed and Temporary Storage]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-06-08T15:17:17Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [mount]() Tags: [blog](), [boot](), [desktop](), [filesystem](), [how-to](), [linux](), [mount](), [performance](), [server](), [storage](), [sysadmins]() ### AI overview A practical guide to Linux tmpfs, a filesystem backed by virtual memory that can use RAM and swap. It explains how Linux uses tmpfs, how to create and verify mounts, how to make them persistent, and when temporary storage is useful. ### Source excerpt tmpfs lets you mount a filesystem entirely in RAM. Here is how Linux already uses it, how to create your own mounts, and where it actually makes sense to use one. Continue reading... ## Drives for Vercel Sandbox in Private Beta DevFeed: [Drives for Vercel Sandbox in Private Beta]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-06-05T00:01:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [DRIVE](), [Vercel](), [mount](), [SDKs](), [Command-line interface]() Tags: [cli](), [dependencies](), [drive](), [mount](), [production](), [sandbox](), [sandboxes](), [sdk](), [storage](), [vercel]() ### AI overview Vercel Sandbox introduces Drives in private beta, providing persistent attachable storage that remains available across disposable sandbox lifecycles. Drives can preserve agent workspaces, repositories, dependencies, and build outputs, and can be managed through the beta SDK or CLI. ### Source excerpt Vercel Sandbox now supports drives in private beta. Drives are persistent, attachable storage with a lifecycle independent from any sandbox. Create a drive once, then mount it at a configurable path when starting a sandbox. When the sandbox stops, the drive remains available to attach to a later sandbox. Install the beta SDK (@vercel/sandbox@beta) or beta CLI (sandbox@beta), then create and mount a drive: Sandbox Drives are useful for: Keeping agent workspaces across disposable sandboxes Retaining cloned repositories, dependencies, and build outputs Managing data independently from the sandbox lifecycle During the private beta, a drive can be mounted read-write by one sandbox at a time. Sandbox drives should not be used for production data while in private beta. Sign up here to join the waitlist, learn more in the docs, or read the complete guide. Read more ## Security Week 2619: особенности уязвимости Copy Fail в ядре Linux DevFeed: [Security Week 2619: особенности уязвимости Copy Fail в ядре Linux]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-05-04T18:24:46Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Linux](), [Security](), [Docker](), [Kubernetes](), [Python](), [Shell](), [mount](), [passwd]() Tags: [2017](), [2026](), [copy-fail](), [cve](), [docker](), [kubernetes](), [linux](), [mount](), [passwd](), [python](), [security](), [tag-9fe8963de219]() ### AI overview This article examines Copy Fail, a Linux kernel vulnerability identified as CVE-2026-31431 with a CVSS score of 7.8. The flaw in the algif_aead module can allow a local attacker to modify the cache of readable files and potentially gain superuser privileges. The article discusses risks to container environments, detection indicators, and mitigations including kernel updates or blocking the module. ### Source excerpt Важной новостью прошлой недели стало обнародование данных об опасной уязвимости в ядре Linux, получившей название Copy Fail (мини-сайт, новость на Хабре), которая открывает относительно простой способ локального повышения привилегий. Авторы оригинального исследования не стесняются рекламировать ИИ-ассистент для анализа кодовой базы, который нашел данную проблему в течение часа. Исследователи "Лаборатории Касперского" провели анализ уязвимости и предложили варианты обнаружения атак с ее использованием. Уязвимость получила идентификатор CVE-2026-31431 и рейтинг 7,8 балла по шкале CVSS. Ошибка была внесена в код модуля ядра algif_aead еще в 2017 году: тогда была внедрена поддержка оптимизаций in-place при работе системы шифрования AEAD. Это, в свою очередь, привело к дефекту обработки буферов, что дало потенциальному атакующему возможность контролируемо изменять содержимое кэша любого файла, доступного для чтения. Читать далее ## Kubernetes v1.36: User Namespaces in Kubernetes are finally GA DevFeed: [Kubernetes v1.36: User Namespaces in Kubernetes are finally GA]() Original publisher: [Read original article]() Author: Rodrigo Campos Catelin; Giuseppe Scrivano Published: 2026-04-23T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Linux](), [mount](), [Security](), [Containers](), [vulnerability]() Tags: [containers](), [kubernetes](), [linux](), [mount](), [performance](), [process](), [security](), [startup](), [vulnerability]() ### AI overview Kubernetes v1.36 brings User Namespaces to General Availability, enabling rootless security isolation for workloads. The Linux-only feature confines container privileges to the user namespace, while ID-mapped mounts translate ownership at mount time without rewriting files or incurring expensive recursive ownership changes. ### Source excerpt After several years of development, User Namespaces support in Kubernetes reached General Availability (GA) with the v1.36 release. This is a Linux-only feature. For those of us working on low level container runtimes and rootless technologies, this has been a long awaited milestone. We finally reached the point where "rootless" security isolation can be used for Kubernetes workloads. This feature also enables a critical pattern: running workloads with privileges and still being confined in the user namespace. When hostUsers: false is set, capabilities like CAP_NET_ADMIN become namespaced, meaning they grant administrative power over container local resources without affecting the host. This effectively enables new use cases that were not possible before without running a fully privileged container. The Problem with UID 0 A process running as root inside a container is also seen from the kernel as root on the host. If an attacker manages to break out of the container, whether through a kernel vulnerability or a misconfigured mount, they are root on the host. While there are many security measures in place for running containers, these measures don't change the underlying identity of the process, it still has some "parts" of root. The engine: ID-mapped mounts The road to GA wasn't just about the Kubernetes API; it was about making the kernel work for us. In the early stages, one of the biggest blockers was volume ownership. If you mapped a container to a high UID range, the Kubelet had to recursively chown every file in the attached volume so the container could read/write them. For large volumes, this was such an expensive operation that destroyed startup performance. The key enabler was ID-mapped mounts (introduced in Linux 5.12 and refined in later versions). Instead of rewriting file ownership on disk, the kernel remaps it at mount time. When a volume is mounted into a Pod with User Namespaces enabled, the kernel performs a transparent translation of the UIDs (us ## SELinux Volume Label Changes goes GA (and likely implications in v1.37) DevFeed: [SELinux Volume Label Changes goes GA (and likely implications in v1.37)]() Original publisher: [Read original article]() Author: Jan Šafránek Swathi Rao Published: 2026-04-22T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [SELinux](), [Kubernetes](), [Linux](), [Security](), [mount]() Tags: [kubernetes](), [linux](), [mount](), [security](), [selinux]() ### AI overview Kubernetes' SELinuxMount feature is expected to become enabled by default in a future release, anticipated to be v1.37. The change can speed up volume setup by avoiding recursive relabeling, but may affect applications that rely on the previous behavior. Kubernetes v1.36 is presented as the release to audit clusters and address compatibility concerns. ### Source excerpt If you run Kubernetes on Linux with SELinux in enforcing mode, plan ahead: a future release (anticipated to be v1.37) is expected to turn the SELinuxMount feature gate on by default. This makes volume setup faster for most workloads, but it can break applications that still depend on the older recursive relabeling model in subtle ways (for example, sharing one volume between privileged and unprivileged Pods on the same node). Kubernetes v1.36 is the right release to audit your cluster and fix or opt out of this change. If your nodes do not use SELinux, nothing changes for you: the kubelet skips the whole SELinux logic when SELinux is unavailable or disabled in the Linux kernel. You can skip this article completely. This blog builds on the earlier work described in the Kubernetes 1.27: Efficient SELinux Relabeling (Beta) post, where the SELinuxMountReadWriteOncePod feature gate was described. The problem to be addressed remains the same, however, this blog extends that same approach to all volumes. The problem Linux systems with Security Enhanced Linux (SELinux) enabled use labels attached to objects (for example, files and network sockets) to make access control decisions. Historically, the container runtime applies SELinux labels to a Pod and all its volumes. Kubernetes only passes the SELinux label from a Pod's securityContext fields to the container runtime. The container runtime then recursively changes the SELinux label on all files that are visible to the Pod's containers. This can be time-consuming if there are many files on the volume, especially when the volume is on a remote filesystem. Caution:If a container uses subPath of a volume, only that subPath of the whole volume is relabeled. This allows two Pods that have two different SELinux labels to use the same volume, as long as they use different subpaths of it. If a Pod does not have any SELinux label assigned in the Kubernetes API, the container runtime assigns a unique random label, so a process that p ## AgentFS with copy-on-write overlay filesystem DevFeed: [AgentFS with copy-on-write overlay filesystem]() Original publisher: [Read original article]() Author: Pekka Enberg Published: 2025-12-31T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [AI-assisted coding](), [SDKs]() Tags: [agents](), [claude-code](), [codex](), [coding](), [git](), [mount](), [python](), [rust](), [sandbox](), [sqlite](), [typescript]() ### AI overview AgentFS adds a copy-on-write overlay filesystem for isolating coding agents while they work on a host repository. Changes are stored in a SQLite-backed writable layer, leaving host files intact. ### Source excerpt AgentFS now ships copy-on-write overlay support via 'agentfs run', letting coding agents work on your repo in an isolated, SQLite-backed sandbox. ## AgentFS with FUSE: SQLite-backed agent state as a POSIX filesystem DevFeed: [AgentFS with FUSE: SQLite-backed agent state as a POSIX filesystem]() Original publisher: [Read original article]() Author: Pekka Enberg Published: 2025-12-08T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [AI-assisted coding](), [SDKs](), [ai observability]() Tags: [agent](), [ai](), [claude-code](), [mount](), [observability](), [rust](), [sdks](), [sqlite](), [typescript]() ### AI overview AgentFS can mount SQLite-backed agent state as a POSIX filesystem through FUSE, so AI coding agents can use standard filesystem and Unix tools without SDK integration. ### Source excerpt Mount a SQLite-backed agent filesystem as a real POSIX filesystem with 'agentfs mount'. Give AI agents full tool compatibility and live observability. ## Top 10 Launches of Launch Week 15 DevFeed: [Top 10 Launches of Launch Week 15]() Original publisher: [Read original article]() Author: Wen Bo Xie Published: 2025-07-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [API keys](), [JSON Web Tokens](), [Apache Iceberg](), [OpenTelemetry](), [Security](), [Amazon S3](), [Deno](), [Figma](), [GitHub](), [mount](), [ui]() Tags: [2](), [apache-iceberg](), [api](), [api-keys](), [cryptographic](), [figma](), [github](), [launch](), [mount](), [npm](), [opentelemetry](), [s3](), [security](), [stripe]() ### AI overview Supabase's Launch Week 15 roundup presents ten product updates, including new API and JWT signing keys, analytics buckets with Apache Iceberg support, OpenTelemetry integrations, Figma Make connectivity, expanded storage limits, Deno 2 Edge Functions, GitHub-optional branching, Supabase UI components, and a Stripe-to-Postgres sync package. ### Source excerpt Highlights from Launch Week 15 ## Persistent Storage and 97% Faster Cold Starts for Edge Functions DevFeed: [Persistent Storage and 97% Faster Cold Starts for Edge Functions]() Original publisher: [Read original article]() Author: Lakshan Perera; Nyannyacha Published: 2025-07-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Amazon S3](), [Filesystems](), [mount](), [SQLite](), [Tokio](), [JavaScript](), [Internet of things](), [Database]() Tags: [boot](), [dependencies](), [environment-variables](), [files](), [iot](), [latency](), [mount](), [postgres](), [s3](), [sqlite](), [storage](), [tokio]() ### AI overview Supabase introduces persistent storage for Edge Functions by mounting S3-compatible buckets, including Supabase Storage Buckets, as directories. The release also reports up to 97% faster and more predictable cold starts by moving workers performing initial script evaluation to a dedicated blocking pool. ### Source excerpt Mount S3-compatible buckets as persistent file storage in Edge Functions with up to 97% faster cold start times. ## How to Fix USB Sticks Mounted as Read-Only DevFeed: [How to Fix USB Sticks Mounted as Read-Only]() Original publisher: [Read original article]() Author: Samuel Njuguna Karanja Published: 2025-06-06T07:56:19Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [USB](), [Linux](), [mount](), [Hardware]() Tags: [administration](), [administration-filesystems-hardware-mount-usb](), [errors](), [filesystem](), [filesystems](), [flash](), [hardware](), [how-to](), [linux](), [mount](), [storage](), [tutorial](), [usb]() ### AI overview This Linux tutorial explains why USB flash drives may be mounted as read-only, including filesystem errors, read-only mount options, physical write protection, and failing flash storage. It also introduces checking the current mount mode with the mount command. ### Source excerpt Learn how to identify and diagnose undesired USB flash drive read-only mounts. The post How to Fix USB Sticks Mounted as Read-Only first appeared on Baeldung on Linux. Related Stories SMB mount Security Modes and Fixing mount error(13): Permission denied in Linux What Is SELinux? Removing Log Files with a Cron Job in Linux ## Kubernetes v1.33: Image Volumes Graduate to Beta DevFeed: [Kubernetes v1.33: Image Volumes Graduate to Beta]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-05-04T00:00:00Z Content type: release Language: en Sources: [Abhimanyu Saharan]() Topics: [Kubernetes v1.33]() Tags: [kubernetes](), [kubernetes-v1-33](), [mount]() ### AI overview Kubernetes v1.33 promotes Image Volumes to beta, enabling OCI artifacts to be mounted directly into pods as read-only volumes. ### Source excerpt Kubernetes v1.33 promotes Image Volumes to beta, letting OCI artifacts mount directly into pods as read-only volumes, boosting portability and efficiency. ## Cash App on PlanetScale Metal DevFeed: [Cash App on PlanetScale Metal]() Original publisher: [Read original article]() Author: Aaron Young Published: 2025-03-11T00:00:00Z Content type: article Language: en Sources: [Cash App Code Blog]() Topics: [migration](), [vitess](), [MySQL](), [Kubernetes](), [Availability](), [Cloud]() Tags: [availability](), [cloud](), [kubernetes](), [migration](), [mount](), [mysql](), [storage](), [vitess]() ### AI overview Cash App describes its migration from self-managed Vitess and MySQL infrastructure in its datacenters to PlanetScale's cloud-managed product, and its subsequent work with PlanetScale to migrate its fleet to PlanetScale Metal. The article explains the original architecture and reports storage-volume degradation, manual shard failovers, and periods when shards could not accept writes. ### Source excerpt Cash App moves to PlanetScale to drive efficiencies ## Listing all mounts in all mount namespaces DevFeed: [Listing all mounts in all mount namespaces]() Original publisher: [Read original article]() Author: Christian Brauner Published: 2024-12-15T23:00:00Z Content type: tutorial Language: en Sources: [Personal blog of Christian Brauner]() Topics: [mount](), [Linux]() Tags: [api](), [introduction](), [linux](), [mount]() ### AI overview A technical explanation of Linux APIs and system calls for retrieving mount information, iterating through mounts and mount subtrees, and listing mounts in other mount namespaces. It also describes retrieving mount namespace IDs and iterating through mount namespaces. ### Source excerpt Introduction [Next page]()