Re: [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Mark Sanchez]

No worries. I'm going in another direction with the ambientweatherapi 
instead. Cheers.

On Monday, December 4, 2023 at 8:16:57 PM UTC-8 Bruno BORDAS wrote:

> I'm not in a position to test right now.
> I would try to merge the compose file from network with the main one. Try 
> to define the MacVLan in the main compose.
>
> If I remember correctly, I separated both because I needed this second 
> network with other containers too.
>
> Sorry, I'm moving home at the moment and not setup yet 😅
> Le 4 déc. 2023, à 20:22, Mark Sanchez  a écrit:
>>
>> Okay. I'll start with the network connection. I have it in the network 
>> folder and have edited the addresses. Do I need to have NGINX installed 
>> already? When I run docker compose up -d it just says "No Service 
>> Selected". I am assuming it doesn't realize it's supposed to run a MACVLAN 
>> network option?
>>
>> When I run docker network ls I see:
>> sudo docker network ls
>> NETWORK ID NAMEDRIVERSCOPE
>> 57223ea2cf02   bridge  bridgelocal
>> 49360022eadb   hosthost  local
>> dab0c8fc1570   nonenull  local
>> 00f80f463ca4   weewx_default   bridgelocal
>>
>> On Monday, December 4, 2023 at 10:01:49 AM UTC-8 Bruno BORDAS wrote:
>>
>>> Woo this was a long time ago 😅
>>> Let me try to remember.
>>>
>>> No ${PWD} (Print Working Directory) is not for a password , but it is 
>>> the location of your source code AKA where is you docker-compose file.
>>>
>>> Without knowing much your errors, difficult to help.
>>>
>>> Le lun. 4 déc. 2023, 18:17, Mark Sanchez >> > a écrit :
>>>
 This is super cool as I have now purchased the same weather station. 
 However, I'm terrible with Docker. I can't seem to get this running. It 
 seems to keep tripping at steps. Right now I'm stuck because something 
 needs to happen with the ${PWD} variable. Do I need to change that to just 
 my password in the docker-compose.yaml file? I appreciate you setting all 
 of this up though!

 On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:

>>> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my 
> own docker image of weewx. 
>
> It runs on Debian stretch, build from sources, with the interceptor 
> driver and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here: 
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it. 
>
> -- 

>>> You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx-user+...@googlegroups.com .

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com
  
 
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1a52d258-2552-47df-b796-9a6fa4582c48n%40googlegroups.com.

Re: [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

I'm not in a position to test right now.
I would try to merge the compose file from network with the main one. Try to 
define the MacVLan in the main compose.

If I remember correctly, I separated both because I needed this second network 
with other containers too.

Sorry, I'm moving home at the moment and not setup yet 😅

Le 4 déc. 2023, 20:22, à 20:22, Mark Sanchez  a écrit:
>Okay. I'll start with the network connection. I have it in the network 
>folder and have edited the addresses. Do I need to have NGINX installed
>
>already? When I run docker compose up -d it just says "No Service 
>Selected". I am assuming it doesn't realize it's supposed to run a
>MACVLAN 
>network option?
>
>When I run docker network ls I see:
>sudo docker network ls
>NETWORK ID NAMEDRIVERSCOPE
>57223ea2cf02   bridge  bridgelocal
>49360022eadb   hosthost  local
>dab0c8fc1570   nonenull  local
>00f80f463ca4   weewx_default   bridgelocal
>
>On Monday, December 4, 2023 at 10:01:49 AM UTC-8 Bruno BORDAS wrote:
>
>> Woo this was a long time ago 😅
>> Let me try to remember.
>>
>> No ${PWD} (Print Working Directory) is not for a password , but it is
>the 
>> location of your source code AKA where is you docker-compose file.
>>
>> Without knowing much your errors, difficult to help.
>>
>> Le lun. 4 déc. 2023, 18:17, Mark Sanchez  a écrit
>:
>>
>>> This is super cool as I have now purchased the same weather station.
>
>>> However, I'm terrible with Docker. I can't seem to get this running.
>It 
>>> seems to keep tripping at steps. Right now I'm stuck because
>something 
>>> needs to happen with the ${PWD} variable. Do I need to change that
>to just 
>>> my password in the docker-compose.yaml file? I appreciate you
>setting all 
>>> of this up though!
>>>
>>> On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS
>wrote:
>>>
>> Dear weewx users.

 After dozens hours of researches and tries, I'm proud to provide my
>own 
 docker image of weewx. 

 It runs on Debian stretch, build from sources, with the interceptor
>
 driver and neowx skin.

 I use it with Pihole to grab the data.
 Everything (I hope) is written in the repo you can find here: 
 https://github.com/MrNonoss/WeewX-Docker

 Feel free to review and comment it. 

 -- 
>>>
>> You received this message because you are subscribed to a topic in
>the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>>
>https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>>
>https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com
>
>>>
>
>>> .
>>>
>>
>
>-- 
>You received this message because you are subscribed to a topic in the
>Google Groups "weewx-user" group.
>To unsubscribe from this topic, visit
>https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>weewx-user+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>https://groups.google.com/d/msgid/weewx-user/290cfa7d-28e3-45a4-b07a-a46dcd52b488n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f5a413b9-452b-4c49-97f6-06583947774a%40gmail.com.

Re: [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Mark Sanchez]

Okay. I'll start with the network connection. I have it in the network 
folder and have edited the addresses. Do I need to have NGINX installed 
already? When I run docker compose up -d it just says "No Service 
Selected". I am assuming it doesn't realize it's supposed to run a MACVLAN 
network option?

When I run docker network ls I see:
sudo docker network ls
NETWORK ID NAMEDRIVERSCOPE
57223ea2cf02   bridge  bridgelocal
49360022eadb   hosthost  local
dab0c8fc1570   nonenull  local
00f80f463ca4   weewx_default   bridgelocal

On Monday, December 4, 2023 at 10:01:49 AM UTC-8 Bruno BORDAS wrote:

> Woo this was a long time ago 😅
> Let me try to remember.
>
> No ${PWD} (Print Working Directory) is not for a password , but it is the 
> location of your source code AKA where is you docker-compose file.
>
> Without knowing much your errors, difficult to help.
>
> Le lun. 4 déc. 2023, 18:17, Mark Sanchez  a écrit :
>
>> This is super cool as I have now purchased the same weather station. 
>> However, I'm terrible with Docker. I can't seem to get this running. It 
>> seems to keep tripping at steps. Right now I'm stuck because something 
>> needs to happen with the ${PWD} variable. Do I need to change that to just 
>> my password in the docker-compose.yaml file? I appreciate you setting all 
>> of this up though!
>>
>> On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:
>>
> Dear weewx users.
>>>
>>> After dozens hours of researches and tries, I'm proud to provide my own 
>>> docker image of weewx. 
>>>
>>> It runs on Debian stretch, build from sources, with the interceptor 
>>> driver and neowx skin.
>>>
>>> I use it with Pihole to grab the data.
>>> Everything (I hope) is written in the repo you can find here: 
>>> https://github.com/MrNonoss/WeewX-Docker
>>>
>>> Feel free to review and comment it. 
>>>
>>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/290cfa7d-28e3-45a4-b07a-a46dcd52b488n%40googlegroups.com.

Re: [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

Woo this was a long time ago 😅
Let me try to remember.

No ${PWD} (Print Working Directory) is not for a password , but it is the
location of your source code AKA where is you docker-compose file.

Without knowing much your errors, difficult to help.

Le lun. 4 déc. 2023, 18:17, Mark Sanchez  a écrit :

> This is super cool as I have now purchased the same weather station.
> However, I'm terrible with Docker. I can't seem to get this running. It
> seems to keep tripping at steps. Right now I'm stuck because something
> needs to happen with the ${PWD} variable. Do I need to change that to just
> my password in the docker-compose.yaml file? I appreciate you setting all
> of this up though!
>
> On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:
>
>> Dear weewx users.
>>
>> After dozens hours of researches and tries, I'm proud to provide my own
>> docker image of weewx.
>>
>> It runs on Debian stretch, build from sources, with the interceptor
>> driver and neowx skin.
>>
>> I use it with Pihole to grab the data.
>> Everything (I hope) is written in the repo you can find here:
>> https://github.com/MrNonoss/WeewX-Docker
>>
>> Feel free to review and comment it.
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CANjD_WsHKCaFYYfvz4O%3Do4FbAM8-mgDk_Pex8cf68m_summ8dw%40mail.gmail.com.

[weewx-user] Re: Docker image with interceptor driver and neowx skin

[Mark Sanchez]

This is great! Thanks for making this. I am still stumbling when trying to 
get the docker image up and running. I'm not Docker savvy though so it's 
been a struggle. Right now, the docker compose command can't seem to get 
past weewx-core being an undefined volume. Is this a directory I need to 
create? Thanks.

On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:

> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my own 
> docker image of weewx. 
>
> It runs on Debian stretch, build from sources, with the interceptor driver 
> and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here: 
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7c850ba3-620a-435f-a5e5-9e17b776943dn%40googlegroups.com.

[weewx-user] Re: Docker image with interceptor driver and neowx skin

[Mark Sanchez]

This is super cool as I have now purchased the same weather station. 
However, I'm terrible with Docker. I can't seem to get this running. It 
seems to keep tripping at steps. Right now I'm stuck because something 
needs to happen with the ${PWD} variable. Do I need to change that to just 
my password in the docker-compose.yaml file? I appreciate you setting all 
of this up though!

On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:

> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my own 
> docker image of weewx. 
>
> It runs on Debian stretch, build from sources, with the interceptor driver 
> and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here: 
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com.

Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

Sure, no problem
I do not make promises to make it work ^^
Le 14/04/2020 03:28:36, Zsolt Máté  a écrit :
I've cloned your git into my home directory.
so it is /home/docker/weewx

Can I send you an email to this address with the ssh credentials?

On Tuesday, April 14, 2020 at 1:24:52 PM UTC+12, Bruno BORDAS wrote:
But tell me where is your work directory
Le 14/04/2020 03:23:04, Zsolt Máté  a écrit :
I can open a port to my portainer as well, that's not an issue. Just tell me 
what you need.

On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
I won't have access to the portainer ui.
However, as you can notice, this network does not use the macvlan driver, but 
the bridge one.
This is probably why it does not work
Le 14/04/2020 03:18:36, Zsolt Máté  a écrit :
I have portainer installed.
If you think It's faster, and you've got time, I can give you access to my 
system via SSH.

[2020-04-14 13_17_06-Window.png]


On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
I do use portainer to have a better view of my containers, images and networks:
https://www.portainer.io/installation/ [https://www.portainer.io/installation/]


The install il very straigtforward:

docker volume create portainer_data && docker run -d -p 8000:8000 -p 9000:9000 
--name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock 
-v portainer_data:/data portainer/portainer tf

With this, you have a web page at localhost:9000 allowing you to monitor and 
configure networks.

I'm still trying to understant why you can't create network with compose
Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
Yeah, probably because you didn't specify networks options, like iface, etc...
Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2

Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I've cloned your git into my home directory.
so it is /home/docker/weewx

Can I send you an email to this address with the ssh credentials?

On Tuesday, April 14, 2020 at 1:24:52 PM UTC+12, Bruno BORDAS wrote:
>
> But tell me where is your work directory
>
> Le 14/04/2020 03:23:04, Zsolt Máté > a 
> écrit :
> I can open a port to my portainer as well, that's not an issue. Just tell 
> me what you need.
>
> On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
>>
>> I won't have access to the portainer ui.
>> However, as you can notice, this network does not use the macvlan driver, 
>> but the bridge one.
>> This is probably why it does not work
>>
>> Le 14/04/2020 03:18:36, Zsolt Máté  a écrit :
>> I have portainer installed.
>> If you think It's faster, and you've got time, I can give you access to 
>> my system via SSH.
>>
>> [image: 2020-04-14 13_17_06-Window.png]
>>
>>
>> On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> I do use portainer to have a better view of my containers, images and 
>>> networks:
>>> https://www.portainer.io/installation/
>>>
>>> The install il very straigtforward:
>>>
>>> docker volume create portainer_data && docker run -d -p 8000:8000 -p 
>>> 9000:9000 --name=portainer --restart=always -v 
>>> /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data 
>>> portainer/portainer tf
>>>
>>> With this, you have a web page at localhost:9000 allowing you to monitor 
>>> and configure networks.
>>>
>>> I'm still trying to understant why you can't create network with compose
>>>
>>> Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
>>> Well, I just ran that command, I have no docker knowledge.
>>> What can I do next?
>>>
>>> On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:

 Yeah, probably because you didn't specify networks options, like iface, 
 etc...

 Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
 I ran docker create network manually
 docker@docker:~/weewx$ docker network create macvlan_macvlan_network
 e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
 Now running docker-compose -d in /weewx returns:
 docker@docker:~/weewx$ docker-compose up -d
 Starting weewx-core ...
 Starting weewx-core ... error

 ERROR: for weewx-core  user specified IP address is supported only when 
 connecting to networks with user configured subnets

 ERROR: for weewx-core  user specified IP address is supported only when 
 connecting to networks with user configured subnets
 ERROR: Encountered errors while bringing up the project.




 On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>
> Well, that's weird...
> I would try to manually create the network.
>
> But it's what I used on my setup, so...
> Please let me know if it works
>
> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
> docker network ls returns:
> Enter code here...NETWORK ID  NAMEDRIVER 
>  SCOPE
> 416109297adbbridge  bridge  local
> 6bad4fea28c7hosthostlocal
> 05ffebe199bcnonenulllocal
>
> First, "docker-compose d" has to be run in /weewx/network, then in 
> /weewx.
> The one in /network returns
> docker@docker:~/weewx/network$ docker-compose up -d
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
>
> the one in weewx is complaining that the network is not there, which 
> is correct.
> docker@docker:~/weewx$ docker-compose up -d
> ERROR: Network macvlan_macvlan_network declared as external, but could 
> not be found. Please create the network manually using `docker network 
> create macvlan_macvlan_network` and try again.
>
>
>
>
>
> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>
>> You have to run two "docker-compose up -d":
>> - One in the network directory
>> - One in the weewx directory
>>
>> Can you check you networks with "docker network ls"?
>> Then maybe you shall adapt the weewx docker-compose with the given 
>> name of the network
>>
>> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
>> Yes, I did.
>> networks:
>>   macvlan_macvlan_network:
>> external: true
>> I renamed the file to docker-compose.yml, as well
>>
>>
>> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Hi, 
>>>
>>> Did you specify the network at the end of the docker-compose?
>>>
>>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>>
>>> networks:
>>> macvlan_macvlan_network:
>>> external: true
>>>
>>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>

Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

But tell me where is your work directory
Le 14/04/2020 03:23:04, Zsolt Máté  a écrit :
I can open a port to my portainer as well, that's not an issue. Just tell me 
what you need.

On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
I won't have access to the portainer ui.
However, as you can notice, this network does not use the macvlan driver, but 
the bridge one.
This is probably why it does not work
Le 14/04/2020 03:18:36, Zsolt Máté  a écrit :
I have portainer installed.
If you think It's faster, and you've got time, I can give you access to my 
system via SSH.

[2020-04-14 13_17_06-Window.png]


On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
I do use portainer to have a better view of my containers, images and networks:
https://www.portainer.io/installation/ [https://www.portainer.io/installation/]


The install il very straigtforward:

docker volume create portainer_data && docker run -d -p 8000:8000 -p 9000:9000 
--name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock 
-v portainer_data:/data portainer/portainer tf

With this, you have a web page at localhost:9000 allowing you to monitor and 
configure networks.

I'm still trying to understant why you can't create network with compose
Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
Yeah, probably because you didn't specify networks options, like iface, etc...
Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      

Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

Well, maybe we can try first the ssh so that i will try to create with 
docker-compose
Le 14/04/2020 03:23:04, Zsolt Máté  a écrit :
I can open a port to my portainer as well, that's not an issue. Just tell me 
what you need.

On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
I won't have access to the portainer ui.
However, as you can notice, this network does not use the macvlan driver, but 
the bridge one.
This is probably why it does not work
Le 14/04/2020 03:18:36, Zsolt Máté  a écrit :
I have portainer installed.
If you think It's faster, and you've got time, I can give you access to my 
system via SSH.

[2020-04-14 13_17_06-Window.png]


On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
I do use portainer to have a better view of my containers, images and networks:
https://www.portainer.io/installation/ [https://www.portainer.io/installation/]


The install il very straigtforward:

docker volume create portainer_data && docker run -d -p 8000:8000 -p 9000:9000 
--name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock 
-v portainer_data:/data portainer/portainer tf

With this, you have a web page at localhost:9000 allowing you to monitor and 
configure networks.

I'm still trying to understant why you can't create network with compose
Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
Yeah, probably because you didn't specify networks options, like iface, etc...
Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686    

Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I can open a port to my portainer as well, that's not an issue. Just tell 
me what you need.

On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
>
> I won't have access to the portainer ui.
> However, as you can notice, this network does not use the macvlan driver, 
> but the bridge one.
> This is probably why it does not work
>
> Le 14/04/2020 03:18:36, Zsolt Máté > a 
> écrit :
> I have portainer installed.
> If you think It's faster, and you've got time, I can give you access to my 
> system via SSH.
>
> [image: 2020-04-14 13_17_06-Window.png]
>
>
> On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
>>
>> I do use portainer to have a better view of my containers, images and 
>> networks:
>> https://www.portainer.io/installation/
>>
>> The install il very straigtforward:
>>
>> docker volume create portainer_data && docker run -d -p 8000:8000 -p 
>> 9000:9000 --name=portainer --restart=always -v 
>> /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data 
>> portainer/portainer tf
>>
>> With this, you have a web page at localhost:9000 allowing you to monitor 
>> and configure networks.
>>
>> I'm still trying to understant why you can't create network with compose
>>
>> Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
>> Well, I just ran that command, I have no docker knowledge.
>> What can I do next?
>>
>> On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Yeah, probably because you didn't specify networks options, like iface, 
>>> etc...
>>>
>>> Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
>>> I ran docker create network manually
>>> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
>>> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
>>> Now running docker-compose -d in /weewx returns:
>>> docker@docker:~/weewx$ docker-compose up -d
>>> Starting weewx-core ...
>>> Starting weewx-core ... error
>>>
>>> ERROR: for weewx-core  user specified IP address is supported only when 
>>> connecting to networks with user configured subnets
>>>
>>> ERROR: for weewx-core  user specified IP address is supported only when 
>>> connecting to networks with user configured subnets
>>> ERROR: Encountered errors while bringing up the project.
>>>
>>>
>>>
>>>
>>> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:

 Well, that's weird...
 I would try to manually create the network.

 But it's what I used on my setup, so...
 Please let me know if it works

 Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
 docker network ls returns:
 Enter code here...NETWORK ID  NAMEDRIVER   
SCOPE
 416109297adbbridge  bridge  local
 6bad4fea28c7hosthostlocal
 05ffebe199bcnonenulllocal

 First, "docker-compose d" has to be run in /weewx/network, then in 
 /weewx.
 The one in /network returns
 docker@docker:~/weewx/network$ docker-compose up -d
 WARNING: Some networks were defined but are not used by any service: 
 macvlan_network

 the one in weewx is complaining that the network is not there, which is 
 correct.
 docker@docker:~/weewx$ docker-compose up -d
 ERROR: Network macvlan_macvlan_network declared as external, but could 
 not be found. Please create the network manually using `docker network 
 create macvlan_macvlan_network` and try again.





 On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>
> You have to run two "docker-compose up -d":
> - One in the network directory
> - One in the weewx directory
>
> Can you check you networks with "docker network ls"?
> Then maybe you shall adapt the weewx docker-compose with the given 
> name of the network
>
> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
> Yes, I did.
> networks:
>   macvlan_macvlan_network:
> external: true
> I renamed the file to docker-compose.yml, as well
>
>
> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>
>> Hi, 
>>
>> Did you specify the network at the end of the docker-compose?
>>
>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>
>> networks:
>> macvlan_macvlan_network:
>> external: true
>>
>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>> Hi Bruno.
>> I'm getting an error while setting up my network.
>>
>> WARNING: Some networks were defined but are not used by any service: 
>> macvlan_network
>> Attaching to
>>
>> My docker compose looks like this:
>> version: '2'
>> networks:
>>   macvlan_network:
>> driver: macvlan
>> driver_opts:
>>   parent: ens18
>> ipam:
>>   config:
>>   

Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

I won't have access to the portainer ui.
However, as you can notice, this network does not use the macvlan driver, but 
the bridge one.
This is probably why it does not work
Le 14/04/2020 03:18:36, Zsolt Máté  a écrit :
I have portainer installed.
If you think It's faster, and you've got time, I can give you access to my 
system via SSH.

[2020-04-14 13_17_06-Window.png]


On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
I do use portainer to have a better view of my containers, images and networks:
https://www.portainer.io/installation/ [https://www.portainer.io/installation/]


The install il very straigtforward:

docker volume create portainer_data && docker run -d -p 8000:8000 -p 9000:9000 
--name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock 
-v portainer_data:/data portainer/portainer tf

With this, you have a web page at localhost:9000 allowing you to monitor and 
configure networks.

I'm still trying to understant why you can't create network with compose
Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
Yeah, probably because you didn't specify networks options, like iface, etc...
Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      0 BMRU
lo       65536      190      0      0 0           190      0      0      0 LRU
veth1a31  1500     1299      0      0 0          1680      0      0      0 BMRU

Do you have an idea what am I doing wrong?



On Monday, November 11, 2019 at 7:09:

Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I have portainer installed.
If you think It's faster, and you've got time, I can give you access to my 
system via SSH.

[image: 2020-04-14 13_17_06-Window.png]


On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
>
> I do use portainer to have a better view of my containers, images and 
> networks:
> https://www.portainer.io/installation/
>
> The install il very straigtforward:
>
> docker volume create portainer_data && docker run -d -p 8000:8000 -p 
> 9000:9000 --name=portainer --restart=always -v 
> /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data 
> portainer/portainer tf
>
> With this, you have a web page at localhost:9000 allowing you to monitor 
> and configure networks.
>
> I'm still trying to understant why you can't create network with compose
>
> Le 14/04/2020 03:07:29, Zsolt Máté > a 
> écrit :
> Well, I just ran that command, I have no docker knowledge.
> What can I do next?
>
> On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>>
>> Yeah, probably because you didn't specify networks options, like iface, 
>> etc...
>>
>> Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
>> I ran docker create network manually
>> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
>> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
>> Now running docker-compose -d in /weewx returns:
>> docker@docker:~/weewx$ docker-compose up -d
>> Starting weewx-core ...
>> Starting weewx-core ... error
>>
>> ERROR: for weewx-core  user specified IP address is supported only when 
>> connecting to networks with user configured subnets
>>
>> ERROR: for weewx-core  user specified IP address is supported only when 
>> connecting to networks with user configured subnets
>> ERROR: Encountered errors while bringing up the project.
>>
>>
>>
>>
>> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Well, that's weird...
>>> I would try to manually create the network.
>>>
>>> But it's what I used on my setup, so...
>>> Please let me know if it works
>>>
>>> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
>>> docker network ls returns:
>>> Enter code here...NETWORK ID  NAMEDRIVER   
>>>SCOPE
>>> 416109297adbbridge  bridge  local
>>> 6bad4fea28c7hosthostlocal
>>> 05ffebe199bcnonenulllocal
>>>
>>> First, "docker-compose d" has to be run in /weewx/network, then in 
>>> /weewx.
>>> The one in /network returns
>>> docker@docker:~/weewx/network$ docker-compose up -d
>>> WARNING: Some networks were defined but are not used by any service: 
>>> macvlan_network
>>>
>>> the one in weewx is complaining that the network is not there, which is 
>>> correct.
>>> docker@docker:~/weewx$ docker-compose up -d
>>> ERROR: Network macvlan_macvlan_network declared as external, but could 
>>> not be found. Please create the network manually using `docker network 
>>> create macvlan_macvlan_network` and try again.
>>>
>>>
>>>
>>>
>>>
>>> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:

 You have to run two "docker-compose up -d":
 - One in the network directory
 - One in the weewx directory

 Can you check you networks with "docker network ls"?
 Then maybe you shall adapt the weewx docker-compose with the given name 
 of the network

 Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
 Yes, I did.
 networks:
   macvlan_macvlan_network:
 external: true
 I renamed the file to docker-compose.yml, as well


 On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>
> Hi, 
>
> Did you specify the network at the end of the docker-compose?
>
> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>
> networks:
> macvlan_macvlan_network:
> external: true
>
> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
> Hi Bruno.
> I'm getting an error while setting up my network.
>
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
> Attaching to
>
> My docker compose looks like this:
> version: '2'
> networks:
>   macvlan_network:
> driver: macvlan
> driver_opts:
>   parent: ens18
> ipam:
>   config:
> - subnet: 192.168.2.0/24
>   gateway: 192.168.2.1
>   ip_range: 192.168.2.240/28
>
> my network interfaces are:
> docker@docker:~/weewx/network$ ifconfig -s -a
> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
> TX-OVR Flg
> docker0   150010611  0  0 0 18836  0  0
>   0 BMRU
> ens18 1500   434686  0 67 0 24242  0  0
>   0 BMRU
> lo   65536  190  0  0 0   190  

Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

I do use portainer to have a better view of my containers, images and networks:
https://www.portainer.io/installation/


The install il very straigtforward:

docker volume create portainer_data && docker run -d -p 8000:8000 -p 9000:9000 
--name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock 
-v portainer_data:/data portainer/portainer tf

With this, you have a web page at localhost:9000 allowing you to monitor and 
configure networks.

I'm still trying to understant why you can't create network with compose
Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
Yeah, probably because you didn't specify networks options, like iface, etc...
Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      0 BMRU
lo       65536      190      0      0 0           190      0      0      0 LRU
veth1a31  1500     1299      0      0 0          1680      0      0      0 BMRU

Do you have an idea what am I doing wrong?



On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
Dear weewx users.
After dozens hours of researches and tries, I'm proud to provide my own docker 
image of weewx.
It runs on Debian stretch, build from sources, with the interceptor driver and 
neowx skin.
I use it with Pihole to grab the data.
Everything (I hope) is written in the repo you can find here: 
https://github.com/MrNonoss/WeewX-Docker 
[https://github.com/MrNonoss/WeewX-Docker]
Feel free to review and comment it.
--
You received this me

Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>
> Yeah, probably because you didn't specify networks options, like iface, 
> etc...
>
> Le 14/04/2020 02:59:14, Zsolt Máté > a 
> écrit :
> I ran docker create network manually
> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
> Now running docker-compose -d in /weewx returns:
> docker@docker:~/weewx$ docker-compose up -d
> Starting weewx-core ...
> Starting weewx-core ... error
>
> ERROR: for weewx-core  user specified IP address is supported only when 
> connecting to networks with user configured subnets
>
> ERROR: for weewx-core  user specified IP address is supported only when 
> connecting to networks with user configured subnets
> ERROR: Encountered errors while bringing up the project.
>
>
>
>
> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>>
>> Well, that's weird...
>> I would try to manually create the network.
>>
>> But it's what I used on my setup, so...
>> Please let me know if it works
>>
>> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
>> docker network ls returns:
>> Enter code here...NETWORK ID  NAMEDRIVER 
>>  SCOPE
>> 416109297adbbridge  bridge  local
>> 6bad4fea28c7hosthostlocal
>> 05ffebe199bcnonenulllocal
>>
>> First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
>> The one in /network returns
>> docker@docker:~/weewx/network$ docker-compose up -d
>> WARNING: Some networks were defined but are not used by any service: 
>> macvlan_network
>>
>> the one in weewx is complaining that the network is not there, which is 
>> correct.
>> docker@docker:~/weewx$ docker-compose up -d
>> ERROR: Network macvlan_macvlan_network declared as external, but could 
>> not be found. Please create the network manually using `docker network 
>> create macvlan_macvlan_network` and try again.
>>
>>
>>
>>
>>
>> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> You have to run two "docker-compose up -d":
>>> - One in the network directory
>>> - One in the weewx directory
>>>
>>> Can you check you networks with "docker network ls"?
>>> Then maybe you shall adapt the weewx docker-compose with the given name 
>>> of the network
>>>
>>> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
>>> Yes, I did.
>>> networks:
>>>   macvlan_macvlan_network:
>>> external: true
>>> I renamed the file to docker-compose.yml, as well
>>>
>>>
>>> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:

 Hi, 

 Did you specify the network at the end of the docker-compose?
 https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml

 networks:
 macvlan_macvlan_network:
 external: true

 Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
 Hi Bruno.
 I'm getting an error while setting up my network.

 WARNING: Some networks were defined but are not used by any service: 
 macvlan_network
 Attaching to

 My docker compose looks like this:
 version: '2'
 networks:
   macvlan_network:
 driver: macvlan
 driver_opts:
   parent: ens18
 ipam:
   config:
 - subnet: 192.168.2.0/24
   gateway: 192.168.2.1
   ip_range: 192.168.2.240/28

 my network interfaces are:
 docker@docker:~/weewx/network$ ifconfig -s -a
 Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
 TX-OVR Flg
 docker0   150010611  0  0 0 18836  0  0
   0 BMRU
 ens18 1500   434686  0 67 0 24242  0  0
   0 BMRU
 lo   65536  190  0  0 0   190  0  0
   0 LRU
 veth1a31  1500 1299  0  0 0  1680  0  0
   0 BMRU

 Do you have an idea what am I doing wrong?


 On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>
> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my 
> own docker image of weewx. 
>
> It runs on Debian stretch, build from sources, with the interceptor 
> driver and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here: 
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it. 
>
> -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.

Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

Yeah, probably because you didn't specify networks options, like iface, etc...
Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      0 BMRU
lo       65536      190      0      0 0           190      0      0      0 LRU
veth1a31  1500     1299      0      0 0          1680      0      0      0 BMRU

Do you have an idea what am I doing wrong?



On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
Dear weewx users.
After dozens hours of researches and tries, I'm proud to provide my own docker 
image of weewx.
It runs on Debian stretch, build from sources, with the interceptor driver and 
neowx skin.
I use it with Pihole to grab the data.
Everything (I hope) is written in the repo you can find here: 
https://github.com/MrNonoss/WeewX-Docker 
[https://github.com/MrNonoss/WeewX-Docker]
Feel free to review and comment it.
--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe].
To unsubscribe from this group and all its topics, send an email to 
weewx...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
 
[https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email&utm_source=footer].

--
You received this message because you are subscribed to a topic in the Google 
Gro

Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>
> Well, that's weird...
> I would try to manually create the network.
>
> But it's what I used on my setup, so...
> Please let me know if it works
>
> Le 14/04/2020 02:39:10, Zsolt Máté > a 
> écrit :
> docker network ls returns:
> Enter code here...NETWORK ID  NAMEDRIVER 
>  SCOPE
> 416109297adbbridge  bridge  local
> 6bad4fea28c7hosthostlocal
> 05ffebe199bcnonenulllocal
>
> First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
> The one in /network returns
> docker@docker:~/weewx/network$ docker-compose up -d
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
>
> the one in weewx is complaining that the network is not there, which is 
> correct.
> docker@docker:~/weewx$ docker-compose up -d
> ERROR: Network macvlan_macvlan_network declared as external, but could not 
> be found. Please create the network manually using `docker network create 
> macvlan_macvlan_network` and try again.
>
>
>
>
>
> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>
>> You have to run two "docker-compose up -d":
>> - One in the network directory
>> - One in the weewx directory
>>
>> Can you check you networks with "docker network ls"?
>> Then maybe you shall adapt the weewx docker-compose with the given name 
>> of the network
>>
>> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
>> Yes, I did.
>> networks:
>>   macvlan_macvlan_network:
>> external: true
>> I renamed the file to docker-compose.yml, as well
>>
>>
>> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Hi, 
>>>
>>> Did you specify the network at the end of the docker-compose?
>>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>>
>>> networks:
>>> macvlan_macvlan_network:
>>> external: true
>>>
>>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>>> Hi Bruno.
>>> I'm getting an error while setting up my network.
>>>
>>> WARNING: Some networks were defined but are not used by any service: 
>>> macvlan_network
>>> Attaching to
>>>
>>> My docker compose looks like this:
>>> version: '2'
>>> networks:
>>>   macvlan_network:
>>> driver: macvlan
>>> driver_opts:
>>>   parent: ens18
>>> ipam:
>>>   config:
>>> - subnet: 192.168.2.0/24
>>>   gateway: 192.168.2.1
>>>   ip_range: 192.168.2.240/28
>>>
>>> my network interfaces are:
>>> docker@docker:~/weewx/network$ ifconfig -s -a
>>> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
>>> TX-OVR Flg
>>> docker0   150010611  0  0 0 18836  0  0  
>>> 0 BMRU
>>> ens18 1500   434686  0 67 0 24242  0  0  
>>> 0 BMRU
>>> lo   65536  190  0  0 0   190  0  0  
>>> 0 LRU
>>> veth1a31  1500 1299  0  0 0  1680  0  0  
>>> 0 BMRU
>>>
>>> Do you have an idea what am I doing wrong?
>>>
>>>
>>> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:

 Dear weewx users.

 After dozens hours of researches and tries, I'm proud to provide my own 
 docker image of weewx. 

 It runs on Debian stretch, build from sources, with the interceptor 
 driver and neowx skin.

 I use it with Pihole to grab the data.
 Everything (I hope) is written in the repo you can find here: 
 https://github.com/MrNonoss/WeewX-Docker

 Feel free to review and comment it. 

 -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> -- 
>> You received

Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

Well, that's weird...
I would try to manually create the network.

But it's what I used on my setup, so...
Please let me know if it works
Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
docker network ls returns:
Enter code here...NETWORK ID          NAME                DRIVER              
SCOPE
416109297adb        bridge              bridge              local
6bad4fea28c7        host                host                local
05ffebe199bc        none                null                local

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not be 
found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      0 BMRU
lo       65536      190      0      0 0           190      0      0      0 LRU
veth1a31  1500     1299      0      0 0          1680      0      0      0 BMRU

Do you have an idea what am I doing wrong?



On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
Dear weewx users.
After dozens hours of researches and tries, I'm proud to provide my own docker 
image of weewx.
It runs on Debian stretch, build from sources, with the interceptor driver and 
neowx skin.
I use it with Pihole to grab the data.
Everything (I hope) is written in the repo you can find here: 
https://github.com/MrNonoss/WeewX-Docker 
[https://github.com/MrNonoss/WeewX-Docker]
Feel free to review and comment it.
--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe].
To unsubscribe from this group and all its topics, send an email to 
weewx...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
 
[https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email&utm_source=footer].

--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe].
To unsubscribe from this group and all its topics, send an email to 
weewx...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com
 
[https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com?utm_medium=email&utm_source=footer].

--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google

Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

docker network ls returns:
Enter code here...NETWORK ID  NAMEDRIVER   
   SCOPE
416109297adbbridge  bridge  local
6bad4fea28c7hosthostlocal
05ffebe199bcnonenulllocal

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is 
correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not 
be found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>
> You have to run two "docker-compose up -d":
> - One in the network directory
> - One in the weewx directory
>
> Can you check you networks with "docker network ls"?
> Then maybe you shall adapt the weewx docker-compose with the given name of 
> the network
>
> Le 14/04/2020 02:05:10, Zsolt Máté > a 
> écrit :
> Yes, I did.
> networks:
>   macvlan_macvlan_network:
> external: true
> I renamed the file to docker-compose.yml, as well
>
>
> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>
>> Hi, 
>>
>> Did you specify the network at the end of the docker-compose?
>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>
>> networks:
>> macvlan_macvlan_network:
>> external: true
>>
>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>> Hi Bruno.
>> I'm getting an error while setting up my network.
>>
>> WARNING: Some networks were defined but are not used by any service: 
>> macvlan_network
>> Attaching to
>>
>> My docker compose looks like this:
>> version: '2'
>> networks:
>>   macvlan_network:
>> driver: macvlan
>> driver_opts:
>>   parent: ens18
>> ipam:
>>   config:
>> - subnet: 192.168.2.0/24
>>   gateway: 192.168.2.1
>>   ip_range: 192.168.2.240/28
>>
>> my network interfaces are:
>> docker@docker:~/weewx/network$ ifconfig -s -a
>> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
>> TX-OVR Flg
>> docker0   150010611  0  0 0 18836  0  0  
>> 0 BMRU
>> ens18 1500   434686  0 67 0 24242  0  0  
>> 0 BMRU
>> lo   65536  190  0  0 0   190  0  0  
>> 0 LRU
>> veth1a31  1500 1299  0  0 0  1680  0  0  
>> 0 BMRU
>>
>> Do you have an idea what am I doing wrong?
>>
>>
>> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>>
>>> Dear weewx users.
>>>
>>> After dozens hours of researches and tries, I'm proud to provide my own 
>>> docker image of weewx. 
>>>
>>> It runs on Debian stretch, build from sources, with the interceptor 
>>> driver and neowx skin.
>>>
>>> I use it with Pihole to grab the data.
>>> Everything (I hope) is written in the repo you can find here: 
>>> https://github.com/MrNonoss/WeewX-Docker
>>>
>>> Feel free to review and comment it. 
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/96c7213f-baf8-4cc1-a968-054292e59a74%40googlegroups.com.

Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

You have to run two "docker-compose up -d":
- One in the network directory
- One in the weewx directory

Can you check you networks with "docker network ls"?
Then maybe you shall adapt the weewx docker-compose with the given name of the 
network
Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
Yes, I did.
networks:

  macvlan_macvlan_network:
    external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml 
[https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml]


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24 [http://192.168.2.0/24]
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28 [http://192.168.2.240/28]

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      0 BMRU
lo       65536      190      0      0 0           190      0      0      0 LRU
veth1a31  1500     1299      0      0 0          1680      0      0      0 BMRU

Do you have an idea what am I doing wrong?



On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
Dear weewx users.
After dozens hours of researches and tries, I'm proud to provide my own docker 
image of weewx.
It runs on Debian stretch, build from sources, with the interceptor driver and 
neowx skin.
I use it with Pihole to grab the data.
Everything (I hope) is written in the repo you can find here: 
https://github.com/MrNonoss/WeewX-Docker 
[https://github.com/MrNonoss/WeewX-Docker]
Feel free to review and comment it.
--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe].
To unsubscribe from this group and all its topics, send an email to 
weewx...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
 
[https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email&utm_source=footer].

--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe].
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
[mailto:weewx-user+unsubscr...@googlegroups.com].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com
 
[https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com?utm_medium=email&utm_source=footer].

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/Mailbird-040aef08-1431-4b71-be6d-4405b28655a4%40gmail.com.

Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

If I'm trying to run docker-compose in the weewx folder, I get this:
ERROR: Network macvlan_macvlan_network declared as external, but could not 
be found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.
Should I run "docker network create macvlan_macvlan_network" manually?

On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>
> Hi, 
>
> Did you specify the network at the end of the docker-compose?
> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>
> networks:
> macvlan_macvlan_network:
> external: true
>
> Le 14/04/2020 01:13:47, Zsolt Máté > a 
> écrit :
> Hi Bruno.
> I'm getting an error while setting up my network.
>
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
> Attaching to
>
> My docker compose looks like this:
> version: '2'
> networks:
>   macvlan_network:
> driver: macvlan
> driver_opts:
>   parent: ens18
> ipam:
>   config:
> - subnet: 192.168.2.0/24
>   gateway: 192.168.2.1
>   ip_range: 192.168.2.240/28
>
> my network interfaces are:
> docker@docker:~/weewx/network$ ifconfig -s -a
> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
> Flg
> docker0   150010611  0  0 0 18836  0  0  0 
> BMRU
> ens18 1500   434686  0 67 0 24242  0  0  0 
> BMRU
> lo   65536  190  0  0 0   190  0  0  0 
> LRU
> veth1a31  1500 1299  0  0 0  1680  0  0  0 
> BMRU
>
> Do you have an idea what am I doing wrong?
>
>
> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>
>> Dear weewx users.
>>
>> After dozens hours of researches and tries, I'm proud to provide my own 
>> docker image of weewx. 
>>
>> It runs on Debian stretch, build from sources, with the interceptor 
>> driver and neowx skin.
>>
>> I use it with Pihole to grab the data.
>> Everything (I hope) is written in the repo you can find here: 
>> https://github.com/MrNonoss/WeewX-Docker
>>
>> Feel free to review and comment it. 
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1a3dff8a-1459-42c0-88a4-1396c5c5774f%40googlegroups.com.

Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

Yes, I did.
networks:
  macvlan_macvlan_network:
external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>
> Hi, 
>
> Did you specify the network at the end of the docker-compose?
> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>
> networks:
> macvlan_macvlan_network:
> external: true
>
> Le 14/04/2020 01:13:47, Zsolt Máté > a 
> écrit :
> Hi Bruno.
> I'm getting an error while setting up my network.
>
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
> Attaching to
>
> My docker compose looks like this:
> version: '2'
> networks:
>   macvlan_network:
> driver: macvlan
> driver_opts:
>   parent: ens18
> ipam:
>   config:
> - subnet: 192.168.2.0/24
>   gateway: 192.168.2.1
>   ip_range: 192.168.2.240/28
>
> my network interfaces are:
> docker@docker:~/weewx/network$ ifconfig -s -a
> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
> Flg
> docker0   150010611  0  0 0 18836  0  0  0 
> BMRU
> ens18 1500   434686  0 67 0 24242  0  0  0 
> BMRU
> lo   65536  190  0  0 0   190  0  0  0 
> LRU
> veth1a31  1500 1299  0  0 0  1680  0  0  0 
> BMRU
>
> Do you have an idea what am I doing wrong?
>
>
> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>
>> Dear weewx users.
>>
>> After dozens hours of researches and tries, I'm proud to provide my own 
>> docker image of weewx. 
>>
>> It runs on Debian stretch, build from sources, with the interceptor 
>> driver and neowx skin.
>>
>> I use it with Pihole to grab the data.
>> Everything (I hope) is written in the repo you can find here: 
>> https://github.com/MrNonoss/WeewX-Docker
>>
>> Feel free to review and comment it. 
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com.

Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Bruno BORDAS]

Hi, 

Did you specify the network at the end of the docker-compose?
https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml


networks:
macvlan_macvlan_network:
external: true

Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:

version: '2'
networks:
  macvlan_network:
    driver: macvlan
    driver_opts:
      parent: ens18
    ipam:
      config:
        - subnet: 192.168.2.0/24
          gateway: 192.168.2.1
          ip_range: 192.168.2.240/28

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
docker0   1500    10611      0      0 0         18836      0      0      0 BMRU
ens18     1500   434686      0     67 0         24242      0      0      0 BMRU
lo       65536      190      0      0 0           190      0      0      0 LRU
veth1a31  1500     1299      0      0 0          1680      0      0      0 BMRU

Do you have an idea what am I doing wrong?



On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
Dear weewx users.
After dozens hours of researches and tries, I'm proud to provide my own docker 
image of weewx.
It runs on Debian stretch, build from sources, with the interceptor driver and 
neowx skin.
I use it with Pihole to grab the data.
Everything (I hope) is written in the repo you can find here: 
https://github.com/MrNonoss/WeewX-Docker 
[https://github.com/MrNonoss/WeewX-Docker]
Feel free to review and comment it.
--
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe 
[https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe].
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
[mailto:weewx-user+unsubscr...@googlegroups.com].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
 
[https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email&utm_source=footer].

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/Mailbird-1ed17e58-208b-43e1-926c-9186a56c4d78%40gmail.com.

[weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:
version: '2'
networks:
  macvlan_network:
driver: macvlan
driver_opts:
  parent: ens18
ipam:
  config:
- subnet: 192.168.2.0/24
  gateway: 192.168.2.1
  ip_range: 192.168.2.240/28

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
Flg
docker0   150010611  0  0 0 18836  0  0  0 
BMRU
ens18 1500   434686  0 67 0 24242  0  0  0 
BMRU
lo   65536  190  0  0 0   190  0  0  0 
LRU
veth1a31  1500 1299  0  0 0  1680  0  0  0 
BMRU

Do you have an idea what am I doing wrong?


On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>
> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my own 
> docker image of weewx. 
>
> It runs on Debian stretch, build from sources, with the interceptor driver 
> and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here: 
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com.