Hei henryk,
thank you for your fast reply.
That’s how i implementet it:
#- 80:80 #optional (for the webinterface)
- 8443:8443 #optional (for the webinterface)
#- 443:443 #Port is needed for the connection for the box, must not be changed
I have searched the topic macvlan and found this artice:
https://forum.revvox.de/t/working-docker-compose-yml-file-for-creating-the-docker-container/81
Can you help with the change of the file:
NAS IP: 192.168.0.100
NAS domainame: LCARS
Gateway/ Router IP: 192.168.0.1
I coosed 192.168.0.25 for the dockervlan because it is in the “hard” ip range from my dhcp.
Here https://forum.revvox.de/t/working-docker-compose-yml-file-for-creating-the-docker-container/81/4?u=stef they write that for Synology NAS you have to change the name from eth0 to ovs_eth0
Here https://forum.revvox.de/t/working-docker-compose-yml-file-for-creating-the-docker-container/81/5?u=stef they write that you can delete the second last line. ( I want to delete it because I dont understand it). If it is not allowed what sould I write instead?
version: '3'
services:
teddycloud:
container_name: teddycloud
mac_address: 66-66-66-00-00-01 # random
networks:
dockervlan:
ipv4_address: 192.168.0.25 # set your own IP-Adress
hostname: teddycloud
domainname: LCARS # set your own domain
image: ghcr.io/toniebox-reverse-engineering/teddycloud:latest
ports:
- 80:80 #optional
- 443:443 #Port is needed for the connection for the box
volumes:
- certs:/teddycloud/certs
- config:/teddycloud/config
- content:/teddycloud/data/content
- library:/teddycloud/data/library
- firmware:/teddycloud/data/firmware
restart: unless-stopped
environment:
- TZ=Europe/Berlin
cap_add:
- NET_ADMIN
volumes:
certs:
config:
content:
library:
firmware:
networks:
dockervlan:
name: dockervlan
driver: macvlan
driver_opts:
parent: ovs_eth0
ipam:
config:
- subnet: "192.168.0.0/24" # change it to your own network address!
#ip_range: "192.168.178.100/26" # change it to your own network address!
gateway: "192.168.0.1" # change it to your own network address!
When I implement this stack I will lose all produced datas (certificates, ..) in the docker volumes? ( I think that should be no problem, isn’t it?)
How is it possible for me to come from this window to the Patch Flash (second point) in order to patch the original firmware with the right IP adress and optional ( wlan ssid and password)?