-
Notifications
You must be signed in to change notification settings - Fork 201
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
pid in container managed by systemd #29
Comments
kuangchanglang
added a commit
to kuangchanglang/xid
that referenced
this issue
Apr 12, 2018
Change-Id: I294c99e94cf341d36fd4721bdd1ef111a76e7a06
This should be fixed already, see #17 |
Oh nevermind, I missed the part when it’s not pid 1. |
kuangchanglang
added a commit
to kuangchanglang/xid
that referenced
this issue
Apr 15, 2018
Change-Id: Ie16e25a9ebac5bee3cda2d4fadc83a864a927399
Fixed by 9c6b126 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys, my server is managed by systemd, running in a docker container, which probably own the same pid(and it's not 1) in different containers. This will cause xid conflict when multi instances deployed in one host.
Any idea to solve this case?
The text was updated successfully, but these errors were encountered: