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
Support full rootless Docker. On localhost (coolify instance) and on connected remote servers.
This will greatly improve the security of the coolify containers and the services running on them, as rootless Docker isolation is required to truly separate each container.
cc @DeVoresyah
Minimal Reproduction (if possible, example repository)
Exception or Error
No response
Version
The text was updated successfully, but these errors were encountered:
A second thing to consider is implementing podman for better security, or even as an addition to docker, since it runs more securely by default (rootless). https://podman.io/
Some more help to implement:
To run Docker as a router, we need to use custom Docker images for all services (so we essentially need to rewrite the services a bit) as we need to use the yml file and the a custom dockerfile for each service:
Issue that adds this: #2552
In each service folder there should be a service.yml file and a custom service.dockerfile, so for example for WordPress: wordpress.yml and DOCKERFILE inside the wordpress service folder.
In the custom docker file we use the flowing command to create a random user that does not have root privileges and disable the root user:
RUN groupadd -r <user> && useradd -r -g <group> <user>
RUN chsh -s /usr/sbin/nologin root
In the yml file we access the image something like this:
service:
build:
context: .
@andrasbacsai if you need more help just let me know.
Description
Support full rootless Docker. On localhost (coolify instance) and on connected remote servers.
This will greatly improve the security of the coolify containers and the services running on them, as rootless Docker isolation is required to truly separate each container.
cc @DeVoresyah
Minimal Reproduction (if possible, example repository)
Exception or Error
No response
Version
The text was updated successfully, but these errors were encountered: