homelab/stack
1
0
Fork 0
Code Issues 115 Pull Requests 1 Actions 3 Packages Projects 1 Releases Wiki Activity

Fix 'no storage connected' in marimo — install obstore/s3fs, wire S3 #81

New Issue
Closed
opened 2026-03-22 00:40:03 +00:00 by kert · 0 comments
kert commented 2026-03-22 00:40:03 +00:00
Owner
Copy Link

Problem

Marimo's Files panel shows 'no storage connected' because:

  1. obstore is not installed in the notebooks container
  2. s3fs is not installed (fsspec knows about s3 protocol but can't import the backend)
  3. No notebook cell creates an obstore/fsspec S3 connection for marimo to auto-discover

Fix

  1. Add obstore and s3fs to notebooks/Dockerfile uv add
  2. Add S3 storage connection to _template.py so new notebooks come pre-wired
  3. Add obstore-s3 snippet to notebooks/snippets/connections.py
  4. Update conf/connect.py with an obstore() factory that returns an S3Store
  5. Test the connection works inside the container

Files

  • notebooks/Dockerfile
  • notebooks/_template.py
  • notebooks/snippets/connections.py
  • src/conf/connect.py
  • tests/conf/test_connect.py
## Problem Marimo's Files panel shows 'no storage connected' because: 1. `obstore` is not installed in the notebooks container 2. `s3fs` is not installed (fsspec knows about s3 protocol but can't import the backend) 3. No notebook cell creates an obstore/fsspec S3 connection for marimo to auto-discover ## Fix 1. Add `obstore` and `s3fs` to notebooks/Dockerfile uv add 2. Add S3 storage connection to `_template.py` so new notebooks come pre-wired 3. Add `obstore-s3` snippet to `notebooks/snippets/connections.py` 4. Update `conf/connect.py` with an `obstore()` factory that returns an S3Store 5. Test the connection works inside the container ## Files - `notebooks/Dockerfile` - `notebooks/_template.py` - `notebooks/snippets/connections.py` - `src/conf/connect.py` - `tests/conf/test_connect.py`
kert added this to the P14: Notebook DX — connections, snippets, templates, S3 buckets milestone 2026-03-22 00:40:03 +00:00
kert added the config label 2026-03-22 00:40:03 +00:00
kert closed this issue 2026-03-22 00:44:07 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label config
Milestone
No items
No Milestone P14: Notebook DX — connections, snippets, templates, S3 buckets
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#81
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?