

Die Versorgungskrise haben die Asiaten. Andererseits fahren die Tanker dorthin, wo es den höchsten Preis gibt.
Die letzte Steuererleichterung für Sprit kam nicht so 100% beim Verbraucher an. Abwarten.


Die Versorgungskrise haben die Asiaten. Andererseits fahren die Tanker dorthin, wo es den höchsten Preis gibt.
Die letzte Steuererleichterung für Sprit kam nicht so 100% beim Verbraucher an. Abwarten.


Ah. I thought there is an option in docker compose I could use.
And a docker image prune - a while the containers are running? :)


I don’t understand. docker compose up starts the container. When does the docker compose pull happen? Or is there an update directive in the compose file?
Is the milk free if you have to work for it? ;)


Do I have to count the dotted lines, too?
Yes. But does it have to be your cow? And can you keep the milk? What does the calf say about that?


Das Parken am Flughafen ist halt sehr teuer und Parkplätze sind limitiert. Klar lässt man sein Auto da nicht 3 Wochen stehen. Und der Zug hält quasi im Flughafen und man ist direkt da.
Da steckt irgendwo eine Erkenntnis drin, die Städte lebenswerter für seine Bewohner machen könnte… Ich komm grad nicht drauf. Naja, vermutlich doch nicht.


Thanks to all replyers. My brain came up with dots per inch, which didn’t make any sense at all.


Netplan config? Sure:
network:
ethernets:
enp35s0:
dhcp4: false
enp36s0:
dhcp4: false
vlans:
enp35s0.100:
id: 100
link: enp35s0
dhcp4: false
enp35s0.101:
id: 101
link: enp35s0
dhcp4: false
bridges:
br0:
# untagged
interfaces: [enp35s0]
dhcp4: false
br0.100:
# vlan 100
interfaces: [enp35s0.100]
dhcp4: false
br0.101:
#vlan 101
interfaces: [enp35s0.101]
dhcp4: true
version: 2
I’m not sure if the version-property is still required. The only interface with an IP is br0.101. Opnsense provides DHCP (v4).
You can attach multiple ethernet-devices to a bridge (which I did not):
br0.100:
interfaces:
- enp35s0.100
- two
- three
I’m not sure if you can attach the docker bridge via netplan - it has to exist at boot time, I think. My docker containers run inside a VM (kvm) with one interface, which sits in one of the VLANs. The VM’s interface is a bridge device (br0.100). The VM ethernet device is attached to the bridge, it receives its IP from the router and behaves like a real server.


It’s a good day for paint and flag dealers in the region. Maybe for some IT guys with knowledge about AIS transponders, too.


I don’t think I know the reason for the issue you’ve described. I don’t have enough information for that.
First thing would be: Is the routing and firewalling OK? Later: DNS. Even later: services reachable?
The Opnsense instance has configured multiple VLANs and zones too? With one server interface in each? The packets between the vlans take a path via the router?
I tried to give my server multiple interfaces on different VLANs once, but ran into problems with that approach. I then added one bridge interface per VLAN to the server and gave it just one IP on one vlan. That way the server isn’t tempted to route things itself or deliver packets on a wrong interface. An entire class of possible errors was removed that way. Docker containers and VMs still can have IPs in their respective VLANs/ nets.
It is worth noting that docker firewalling and ufw don’t play well together, which could be the reason for unreachable services. Moving the docker host into a LXC abstracts the issue away. Incus can run OCI containers itself and may be an alternative to docker (but not docker compose).
I can’t say anything about over-engeering. It is a hobby after all and you decide what is important and how much complexity you need. :)
Ok. So if it has a cat face: it might be Renaissance or it is newer but it surely isn’t medieval.
The other way around: if it has a human like face it is medieval or Renaissance.
Noted.


Puh. Meins ist noch da.
How can I tell the difference?


12 in a circle and one in the center, you say? Now I think of an opossum clock.
Wenn Leute das glauben, fahren sie weniger? Das ist doch was gutes?