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

Investigate purpose of Docker socket API #140

Open
mfarina1 opened this issue Sep 25, 2024 · 1 comment
Open

Investigate purpose of Docker socket API #140

mfarina1 opened this issue Sep 25, 2024 · 1 comment
Labels
bug Something isn't working CRIT-3 Defect has moderate to mild impact on usability of delivered software for mission operations.
Milestone

Comments

@mfarina1
Copy link
Collaborator

For Podman, is the Docker socket API truly only used for the mapping of Docker's socket, so that one of the containers can query the status of Docker services? Currently it's not working, but the real question is if it's doing anything other than monitoring the various Docker services? If that's all it's doing, there's probably a better way of doing it that's less dependent on infrastructure

@mfarina1 mfarina1 added the bug Something isn't working label Sep 25, 2024
@mfarina1 mfarina1 added this to the ANMS v1.2.0 milestone Sep 25, 2024
@mfarina1 mfarina1 added this to ANMS Sep 25, 2024
@github-project-automation github-project-automation bot moved this to Todo in ANMS Sep 25, 2024
@mfarina1
Copy link
Collaborator Author

Comment from David Edell: "The only piece I’ve seen so far that is specific to docker is the mounted docker.sock that I suspect is only being used to drive the “Services” status page in the ANMS UI. I believe there is a way podman on the host system can be configured to preserve that functionality. If that is the only thing that socket is used for though, it would probably make more sense in the long-term to replace it with something more generic (which could also work if the components are later distributed to physical systems). "

@mfarina1 mfarina1 added the CRIT-3 Defect has moderate to mild impact on usability of delivered software for mission operations. label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CRIT-3 Defect has moderate to mild impact on usability of delivered software for mission operations.
Projects
Status: Todo
Development

No branches or pull requests

1 participant