about the incus container setup that i have ...
1. each container got their own local ip, which they can communicate with each other via a bridge
2. the host can access to the services that those containers bind on their container without the need of tcp forward or similar
so, basically,
caddy(host) -> 10.xx.xx.6 akkoma(container) -> akkoma backend -> 10.xx.xx.5 postgresql(container) -> postgresql backend
since it's done because of bridge, there should have no performance impact at all.
Yonle
npub1x3…3g4el
2026-01-11 15:56:54 UTC
Author Public Key
npub1x3azxuysp5vmfer4vgs4jn5tmfcx4ew8sh0qnev7gczljxsr7jwqa3g4elPublished at
2026-01-11 15:56:54 UTCEvent JSON
{
"id": "e04e566df7a2260ab93bab67c0ceab8729079b1969749a9dd9a90da7763da2b5",
"pubkey": "347a2370900d19b4e4756221594e8bda706ae5c785de09e59e4605f91a03f49c",
"created_at": 1768147014,
"kind": 1,
"tags": [
[
"alt",
"A short note: about the incus container setup that i have ...\r\n1..."
]
],
"content": "about the incus container setup that i have ...\r\n1. each container got their own local ip, which they can communicate with each other via a bridge\r\n2. the host can access to the services that those containers bind on their container without the need of tcp forward or similar\n\nso, basically,\n\ncaddy(host) -\u003e 10.xx.xx.6 akkoma(container) -\u003e akkoma backend -\u003e 10.xx.xx.5 postgresql(container) -\u003e postgresql backend\n\nsince it's done because of bridge, there should have no performance impact at all.",
"sig": "f1583ddd50c64c795c43e495eefd6c6d1f2efbbe55f73bd5590ac3fa02a91fadaef1257acc77a87c122d44f7f4750ff29d55905c59e4b05d76d00b46b0ee996a"
}