tilt-dev / tilt-dev/tilt

Tilt does not show logs after restarting a container (docker-compose)

Open
#6,041 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Expected Behavior

Tilt UI should continue showing logs of a container after it restarts.

Current Behavior

After a container restarts, Tilt UI no longer shows the output of the container.

Steps to Reproduce

Using the tilt provided example.

git clone https://github.com/tilt-dev/tilt-example-docker-compose
cd tilt-example-docker-compose
tilt up

Go to UI & restart the app container. It does not output expected "Server listening on port 3000" like it does on initial start.

Context
tilt doctor Output

Tilt: v0.31.2, built 2023-02-10
System: linux-amd64

Docker

  • Host: unix:///var/run/docker.sock
  • Server Version: 23.0.1
  • API Version: 1.42
  • Builder: 2
  • Compose Version: v2.14.1

Kubernetes

  • Env:
  • Context:
  • Cluster Name: Unknown
  • Namespace: default
  • Container Runtime: unknown
  • Version: Error: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
  • Cluster Local Registry: none

About Your Use Case

Unable to develop effectively since I can't see logs after restarting.

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the issue using the tilt-example-docker-compose repository, then run tilt up and restart the app container from the UI. Trace the Docker Compose log handling around the restart and verify that the UI again shows the container's subsequent output, including "Server listening on port 3000".

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, go
Domain
devops, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.