Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixing logs between different containers #132

Closed
camohob opened this issue Aug 27, 2018 · 8 comments
Closed

Mixing logs between different containers #132

camohob opened this issue Aug 27, 2018 · 8 comments

Comments

@camohob
Copy link

camohob commented Aug 27, 2018

When i have 2 or more containers from same image - logs are mixed between different containers and different projects. After refresh log - all is ok.
image
on screenshot you can see 'node_1' container log in project which not contain this container.

@igor-lemon
Copy link
Member

Hi @camohob. Thanks for the issue. I'll check your case and write results.

@camohob
Copy link
Author

camohob commented Aug 29, 2018

Hi @igor-lemon, new details: this problem is not related to the same images. When I just run the dockstation (if the projects have already started earlier) - everything is fine, but after restarting any project - the logs are mixed between projects and containers.

@igor-lemon
Copy link
Member

Hi @camohob So, we tried to reproduce your issue and couldn't do it. :(
I wanna find a reason of the problem. Can you record video with your issue?
Need to

  1. Show logs before project restart
  2. After
  3. Show logs from some other project
  4. Show container logs from a terminal docker logs CONTAINER_ID/CONTAINER_NAME

@camohob
Copy link
Author

camohob commented Sep 15, 2018

Hi @igor-lemon, I record video. As you can see - the problem also appears when switching between projects.

@igor-lemon
Copy link
Member

I apologize for the long answer. Ok, thanks for the video. We'll check this case.

@igor-lemon
Copy link
Member

Hi @camohob. We've good news, we found and fixed the bug. Fixes will be able in the v1.5

@camohob
Copy link
Author

camohob commented Jun 27, 2019

Hi @camohob. We've good news, we found and fixed the bug. Fixes will be able in the v1.5

The problem still remain...

@igor-lemon
Copy link
Member

It's strange because we fixed this.
So, I'll recheck this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants