feat(DoutD): enable worker to spawn containers on host (ADAnalise-container) #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
luabida
force-pushed
the
adanalise-dag
branch
2 times, most recently
from
1075c64 to
b28dced
Compare
fccoelho
approved these changes
Mar 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To enable airflow to run ADAnalise-container in a task, I need to make the worker container connect to /var/run/docker.sock on host, so it can spawn a container from outside its own container. I'm not sure what the implications of it in the system, but since the non-root user has the same UID and GID as the host, the permissions shouldn't be a problem, I've been testing locally and I could make the adanalise container to spawn and run it accessing the infodengue's DB thought the docker network