On Thursday, October 7, 2021 at 11:40:06 AM UTC-7 do...@dougjenkins.com
wrote:
> Docker Compose will not allow you to directly map a file (eg weewx.conf)
> from your host to a target file inside a container.
>
>
It does for me. I run my ecowitt weewx instance in docker that way.
services:
weewx:
volumes:
- weewx-ecowitt-html:/home/weewx/public_html
- weewx-ecowitt-archive:/home/weewx/archive
- weewx-ecowitt-ssh:/root/.ssh
- weewx-ecowitt-logs:/var/log
- ${PWD}/configs/weewx.conf:/home/weewx/weewx.conf
> the other problem is device mapping. I am using Accurite 5n1 weather
> station that its display is plugged in via USB to a machine. I am trying to
> map the /dev/bus folder via volumes to the container, but WeeWX fails its
> LOOP generation as the USB is not readable.
>
>
I've done this with the zWave dongle device that I use for Home Assistant
with a specified device, but not with the whole folder.
services:
homeassistant:
devices:
- /dev/ttyACM0:/dev/ttyACM0
I am researching the device mapping as I do not want to run my container in
> privileged mode unless there is no option.
>
>
That I can't help you with other than to suggest using podman, which did
seem to work unprivileged when I tried it in early 2020, but it wasn't a
fully functional docker replacement for me on x86_64 at that time and it
was a bit odd in the hoops you needed to do to get it to run unprivileged.
I haven't kept up with it since then so maybe today's story is more
promising.
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-development/dfc5dfcf-c096-4753-b232-b10a0493a9cen%40googlegroups.com.
