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é <lop...@gmail.com <javascript:>> 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é <lop...@gmail.com> 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é <lop...@gmail.com> 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é <lop...@gmail.com> 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
>>>>>
>>>>> 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
>>>>  
>>>> <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.
>>> 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.
>> 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/96c7213f-baf8-4cc1-a968-054292e59a74%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/96c7213f-baf8-4cc1-a968-054292e59a74%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.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/7dce730c-f537-4970-96cf-77590f3694d4%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/7dce730c-f537-4970-96cf-77590f3694d4%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/6b08d290-592a-44e3-9975-e2186c38ef20%40googlegroups.com.

Reply via email to