Docker container crash with eebus config

[ecfmau]

Hello,
I installed the Docker andig/evcc image on my Synology NAS. It works well with the demo configuration as well as with a partial configuration of my system.
I have an eebus compatible wallbox. I created the eebus configuration from the docker container (public and private certs). As soon as I put the eebus certificates and my wallbox in the config file, the Docker container crashes immediately. Although I set the log levels to trace in the config file, the only entries are the following:

[main  ] INFO 2022/06/26 23:47:24 evcc 0.95
[main  ] INFO 2022/06/26 23:47:24 using config file /etc/evcc.yaml
[main  ] INFO 2022/06/26 23:47:24 listening at :7070

If I remove the eebus config and set another charger, then the Docker container starts and works fine (except the wallbox which obviously reports an error).

Did someone manage to make the eebus configuration work with Docker on a Synology?

I attach my config files: with and without docker.

Thanks for your help and best regards
Fred

evcc_eebus.yaml.txt
evcc_dummycharger.yaml.txt

[andig]

Do you get the same crash without eebus? Does a previous version, say 0.90, work for you? No additional crash info, panic in the logs?

[andig]

Found it. You have the usual problem with machineid on Docker!

[ecfmau]

Ok... Thanks a lot, good that you found it but I'm a bit puzzled... What is the machineid, why does it crash the container whenever I use an eebus config within evcc and do you have any hints on how I can solve the problem?

[andig]

Please search the discussions- this has come up before.

[ecfmau]

Ok thanks, I'll try this tonight when I'm back home.

[StefanSchoof]

Now I get a helping error message:

$docker run --rm -v $(pwd)/evcc.yaml:/etc/evcc.yaml -p 7070:7070 andig/evcc:nightly
[main  ] INFO 2022/06/29 18:20:54 evcc 0.95 (d622b9b7)
[main  ] INFO 2022/06/29 18:20:54 using config file /etc/evcc.yaml
[main  ] INFO 2022/06/29 18:20:54 listening at :7070
[main  ] FATAL 2022/06/29 18:20:54 eebus: machineid: machineid: open /etc/machine-id: no such file or directory

[andig]

Fix is in #3727

[ecfmau]

The machine-id trick indeed solved the crash issue, thanks a lot @andig !

If, like me, you don't have an /etc/machine-id file in your Synology, just create one with an arbitrary, 32 hexadecimal string terminated by a newline. I attached an example (I had to add .txt otherwise Github wouldn't allow me to upload it). Store it somewhere in your file system and map it as /etc/machine-id in the Docker container configuration.

Have fun!

machine-id.txt

[ecfmau]

Closed