Skip to content

ci: fix docker container check #398

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

Merged
merged 1 commit into from
Aug 11, 2016
Merged

Conversation

posborne
Copy link
Member

Newer version of docker no longer have the /.dockerinit file present
when the container is executing, so that is no longer an option.
When executing in a container, we do know that we will be executing
as pid 1 -- this is probably not ever the case on the host system.

r? @fiveop

Newer version of docker no longer have the /.dockerinit file present
when the container is executing, so that is no longer an option.
When executing in a container, we do know that we will be executing
as pid 1 -- this is probably not ever the case on the host system.

Signed-off-by: Paul Osborne <[email protected]>
@fiveop
Copy link
Contributor

fiveop commented Aug 11, 2016

Given that the correct build (pr) is green, it would probably be alright to merge this. Let's see whether homu let's me. Why did the push build trigger?

@homu r+

@homu
Copy link
Contributor

homu commented Aug 11, 2016

📌 Commit 90269e4 has been approved by fiveop

@homu
Copy link
Contributor

homu commented Aug 11, 2016

⚡ Test exempted - status

@homu homu merged commit 90269e4 into nix-rust:master Aug 11, 2016
homu added a commit that referenced this pull request Aug 11, 2016
ci: fix docker container check

Newer version of docker no longer have the /.dockerinit file present
when the container is executing, so that is no longer an option.
When executing in a container, we do know that we will be executing
as pid 1 -- this is probably not ever the case on the host system.

r? @fiveop
@posborne
Copy link
Member Author

Why did the push build trigger?

I accidentally pushed my branch to the wrong remote (this repo) at first.

@posborne posborne deleted the fix-docker-builds branch August 11, 2016 05:03
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

Successfully merging this pull request may close these issues.

3 participants