If your Kubernetes Deployment contains multiple containers started from images
defined in devspace.yaml then devspace dev starts to stream logs only from one of
the containers.
- Start local Kubernetes cluster on Docker for Mac
devspace build -b --skip-pushdevspace dev- Observe the log stream
- Make a change in
index.jsand save it - You should see updates in the log stream (step 3)
- You only see updates from one of the containers started from the images defined in
devspace.yaml
After a developer starts devspace dev then all the logs from different containers (even if they are in the same pod)
should be shown in the log stream.