Docker images are not versioned - everything is `latest`

Open
#150 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker

Research direction

No files, tests, or entry points are named. Start by tracing how Docker images are built and tagged, then determine the repository's expected versioning and rollback behavior. Done means images no longer rely only on the mutable latest tag and production users can identify and pin a stable version.

Written by the indexing model from the issue text.

Description

Chore Infrastructure

Your Docker images have no versioning whatsoever - everything gets tagged as latest. This is causing real problems:

  • I rebuild my template and suddenly my app stops working
  • No way to know what changed or roll back to a working version
  • Can't pin to a stable version for production use
  • Every rebuild is a gamble

Impact

This makes it impossible to use your platform reliably in production. When something breaks, there's no way to identify if it's due to your recent changes or debug what went wrong.

I shouldn't have to avoid rebuilding templates because I'm afraid my application will randomly break.

Dominant language
Python
Stars
2.4k
Forks
228
Avg merge
48m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from e2b-dev/code-interpreter

All issues in e2b-dev/code-interpreter

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.