starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 16:06:04 +03:00

[GH-ISSUE #726] Create a Separate Custom Network in docker-compose.yml for Better Isolation #472

New issue

Closed

opened 2026-03-02 11:50:09 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 11:50:09 +03:00

Owner

Originally created by @Lumpish3007 on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/726

Describe the feature you'd like

I suggest creating a custom network in the docker-compose.yml for better isolation between containers, enhancing security and manageability of the Hoarder environment.

Describe the benefits this would bring to existing Hoarder users

Improved Network Isolation: Creating a separate custom network will allow Hoarder users to control and isolate the communication between the Hoarder services (e.g., web, chrome, meilisearch), preventing potential interference from other containers on the default Docker bridge network.
Custom IP Range Control: Users can specify a custom subnet to avoid IP conflicts with other networks.
Security: Limits communication to relevant containers, improving overall security.
Cleaner Configuration: Simplifies networking management and troubleshooting between containers.

Can the goal of this request already be achieved via other means?

Yes. Users can manually create a custom network in their own docker-compose.yml, but having a default custom network would make the process more streamlined and ensure consistent behavior across different environments without manual intervention.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

Additional context

A custom network could be added like this in the docker-compose.yml:

networks:
  hoarder_network:
    driver: bridge

Originally created by @Lumpish3007 on GitHub (Dec 10, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/726 ### Describe the feature you'd like I suggest creating a custom network in the docker-compose.yml for better isolation between containers, enhancing security and manageability of the Hoarder environment. ### Describe the benefits this would bring to existing Hoarder users - **Improved Network Isolation**: Creating a separate custom network will allow Hoarder users to control and isolate the communication between the Hoarder services (e.g., `web`, `chrome`, `meilisearch`), preventing potential interference from other containers on the default Docker bridge network. - **Custom IP Range Control**: Users can specify a custom subnet to avoid IP conflicts with other networks. - **Security**: Limits communication to relevant containers, improving overall security. - **Cleaner Configuration**: Simplifies networking management and troubleshooting between containers. ### Can the goal of this request already be achieved via other means? Yes. Users can manually create a custom network in their own `docker-compose.yml`, but having a default custom network would make the process more streamlined and ensure consistent behavior across different environments without manual intervention. ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### Additional context A custom network could be added like this in the `docker-compose.yml`: ```yaml networks: hoarder_network: driver: bridge

kerem closed this issue

2026-03-02 11:50:09 +03:00

kerem commented

2026-03-02 11:50:10 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Dec 10, 2024):

@Lumpish3007 docker does automatically create an isolated bridge network for the containers in the compose file called "hoarder_default"

@MohamedBassem commented on GitHub (Dec 10, 2024): @Lumpish3007 docker does automatically create an isolated bridge network for the containers in the compose file called "hoarder_default"

kerem commented

2026-03-02 11:50:10 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Dec 10, 2024):

reference: https://docs.docker.com/compose/how-tos/networking/

@MohamedBassem commented on GitHub (Dec 10, 2024): reference: https://docs.docker.com/compose/how-tos/networking/

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#472

No description provided.

Rows
Columns