Episode: T.20260416.R03.infraestructura.docker.diagnosticar

This commit is contained in:
Ember 2026-04-16 23:28:48 +00:00
parent 7d04b19431
commit 54f56104b1

View file

@ -0,0 +1,25 @@
<!-- EMBER_CROSS_REF
eri: S20260416_PIPELINE_troubleshooting_docker
qdrant_id: 6fee8d44-6dd1-4c68-bbf6-69fa7b09f9b8
qdrant_collection: ember_experience
neo4j_node: (:Episode {id: 'S20260416_PIPELINE_troubleshooting_docker'})
pg_table: episodes
pg_qdrant_id: 6fee8d44-6dd1-4c68-bbf6-69fa7b09f9b8
nc_path: /EMBER/episodios/2026/04/T.20260416.R03.infraestructura.docker.diagnosticar.md
created_at: 2026-04-16T23:28:43+00:00
codex_ref: S20260416.PIPELINE_RECOVERY_CRISOL_HOOK.R3.UID1000_VERIFY
puente: T.20260416.R03.infraestructura.docker.diagnosticar
temp: H9
visibility: V
graph_session: S20260416.R03
graph_domain: infraestructura
graph_entity: docker
graph_action: diagnosticar
mode: troubleshooting
hope_score: 0.421
entities: 1
-->
# troubleshooting: Docker — EPISODIO VERIFICACION UID1000 S20260416_20260416_232843: Este episodio verifica que...
EPISODIO VERIFICACION UID1000 S20260416_20260416_232843: Este episodio verifica que run_from_inbox.py ejecutado con uid 1000 escribe el push_log.jsonl al path persistente /home/johnember/data/logs/ en vez del fallback /tmp/. El container ember-mcp corre con cap_drop ALL y no-new-privileges, lo que impide que root (uid 0) escriba en archivos owned por uid 1000. La solucion es ejecutar el script como uid 1000 usando docker exec -u 1000.