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 MacVL
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 m
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 opt
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 écr
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, Brun
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
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,
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 w
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 brid
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 ca
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, imag
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:/va
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 do
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
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 we
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
416
docker network ls returns:
Enter code here...NETWORK ID NAMEDRIVER
SCOPE
416109297adbbridge bridge local
6bad4fea28c7hosthostlocal
05ffebe199bcnonenull
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
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 mac
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/Weew
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.
21 matches
Mail list logo
