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

Containers do not always start fully #187

Closed
achekulaev opened this issue Apr 24, 2017 · 2 comments
Closed

Containers do not always start fully #187

achekulaev opened this issue Apr 24, 2017 · 2 comments
Assignees
Labels

Comments

@achekulaev
Copy link
Member

In some cases containers start but the following 2 lines:

...
_set_cli_uid && \
_vhost_proxy_connect

Are not executed. This leads to issues with file permissions or site access.

This is how it looks when it fails:

no-start

This is how it should be:

yes-start

@achekulaev achekulaev added this to the 1.3 milestone Apr 24, 2017
@lmakarov lmakarov changed the title Containers does not always start fully Containers do not always start fully May 3, 2017
@achekulaev
Copy link
Member Author

achekulaev commented May 4, 2017

So conditions do work. The thing is that permissions change happens only once, when uid is not set. Basically once after container was created and never again.

I don't know if we should consider doing it every time.

@achekulaev achekulaev removed this from the 1.3 milestone May 6, 2017
@achekulaev
Copy link
Member Author

Most like it is related to #225 . Closing in favor of that one

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

No branches or pull requests

1 participant