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

Re-Validate aufs crawling on Armada #308

Open
canturkisci opened this issue Jun 2, 2017 · 1 comment
Open

Re-Validate aufs crawling on Armada #308

canturkisci opened this issue Jun 2, 2017 · 1 comment

Comments

@canturkisci
Copy link
Member

Description

We have an issue on crawling aufs backed containers. Let us validate we can crawl containers backed by aufs.

Previously we had issues on 'detecting' new containers on an aufs-backed system. We should better understand and document the current state.

How to Reproduce

  • Deploy crawler on armada worked, backed by aufs
  • Validate it (a) discovers and (b) crawls existing containers
  • Check if it (a) discovers and (b) crawls newly-created containers

Related Issues

#112 #167 #275

@nadgowdas
Copy link
Contributor

@canturkisci
Summary of Discussion with Alan:

  1. There is a scenario in which setns fails if called from multi-threaded process. And in namespace.py -> run_as_another_process() the multi-threaded context fails the setns to mount namespace of container. And this is specific to aufs. We don't expect this will be fixed in aufs since its development seems to be stagnant.

  2. Alan mentioned, he has a solution for that and he will create a PR to add that fix into this OSS code.

  3. We also have few gaps in terms of porting few other changes regarding package crawling that we will perform after aufs fix.

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

No branches or pull requests

2 participants