You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did not figure out how to do many things regarding containers.
We have two goals, based on the fact, that EVERY installation, if available, should use docker and not be tried with compilations or distro packages.
Docker inside of the Agent Zero container ?
As based on Kali Linux, Docker installation is already a problem.
The docker-cli may be possible, but seems little helpful.
So, what would be a benefit (but may be a collission with 2)) : Running docker in the container.
The Dind approach is very confusing. The agent does not understand this.
Can we not use Debian stable for Agent Zero?
I could build it on top of debian:bookworm. All installations went through, but the container did not work yet.
Is python 3.13 required?
Missing Tools for host docker containers (neighbors)
We let the agent configure a Docker stack with Dockerfile and yml and directories.
This is mapped into the agent container.
After changes in this app data, it could be required to restart the container.
If the Agent does not have a tool to restart or rebuild containers, it is heavily depending our our "help".
This is NOT THE IDEA.
Opening the docker.socket for rw is also not the idea.
Where are such tools?
The benefit of Docker installations is well known.
In the current setup , the agent is completely paralysed. It does not even understand the problem.
Can we offer tools to start / restart/ build/ rebuild (+ more?) host containers?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I did not figure out how to do many things regarding containers.
We have two goals, based on the fact, that EVERY installation, if available, should use docker and not be tried with compilations or distro packages.
Docker inside of the Agent Zero container ?
As based on Kali Linux, Docker installation is already a problem.
The docker-cli may be possible, but seems little helpful.
So, what would be a benefit (but may be a collission with 2)) : Running docker in the container.
The Dind approach is very confusing. The agent does not understand this.
Can we not use Debian stable for Agent Zero?
I could build it on top of debian:bookworm. All installations went through, but the container did not work yet.
Is python 3.13 required?
Missing Tools for host docker containers (neighbors)
We let the agent configure a Docker stack with Dockerfile and yml and directories.
This is mapped into the agent container.
After changes in this app data, it could be required to restart the container.
If the Agent does not have a tool to restart or rebuild containers, it is heavily depending our our "help".
This is NOT THE IDEA.
Opening the docker.socket for rw is also not the idea.
Where are such tools?
The benefit of Docker installations is well known.
In the current setup , the agent is completely paralysed. It does not even understand the problem.
Can we offer tools to start / restart/ build/ rebuild (+ more?) host containers?
Beta Was this translation helpful? Give feedback.
All reactions