- conflicting ports? Do you already use the mapped ports?
- Macvlan prevents communication from the docker host to the macvlan IP and vice versa. Depending on how and from where you access the macvlan IP, it might not work natively.
- Is NPM starting correctly? No errors in the container logs?
sk1nT7
joined 2 years ago
3 nodes are nice. However, it's just a playground and in a personal lab nothing is that crucial to have high uptime.
Most of the time, all your nodes will die at the same time due to power outage or your ISP fails. As you likely won't have a fallback for these things, operating 3 nodes is likely useless.
If you want to play with kubernes etc. you can do so on a single node too. Just spawn multiple VMs or LXCs in Proxmox. That's enough to learn and play. Of course, having real physical nodes and a real HA cluster is different but you get what I mean hopefully.
Personally, I would take the most modern and powerful server and keep it down to one node.
Usually, when using macvlan, the ports should not conflict as the container obtains a new, separate IP address. What happens if you use bridge networt and manually map the port 80 and 443 port to a random one on your synology like 8888 and 9999?