starting over and have an issue running docker-compose up -d
error is command not found
googling as i post this.
ok just installed
apt install docker-compose
my bad.
starting over and have an issue running docker-compose up -d
error is command not found
googling as i post this.
ok just installed
apt install docker-compose
my bad.
Thanks you, up and running.
copying into nano is a waste. you loose all formatting. if there is a way to keep formatting please share for future use.
so editing the yml file was the hardest part, just wrote everything by hand and made sure all my indexes were correct.
first time had errors about line 17 row 4.
took me a minute too figure what line was wrong.
other than that it's up and running, thank you so much, to macom. and you morlan.
cheers
Quick question.
Is duckdns container used to make sure the IP and DNS are synced?
I might try and change the DNS to dyndns, I have been using that for years. I'm thinking I would have to just go in and edit the IP when it changes.
Is my logic right?
Sent from my S10 using my thumbs, with tapatalk.
Yes, duckdns docker updates your ip. If you have that function elsewhere (e.g. in your router) you can delete the docker.
Glad the guide worked for you.
copying into nano is a waste. you loose all formatting. if there is a way to keep formatting please share for future use.
What do you mean with "loose all formatting". Below is how it looks when I do it on my system. Formatting is there.
If you are looking for line numbers have a look here
https://askubuntu.com/question…-nano-when-opening-a-file
When I hit crtl, shift, v.
Everything copied in but it was on one line. I started to go to each line and hit return. That was taking too much time.
So I just typed it in.
The error I mentioned about line 17 row 4. Was I needed to indent
Volumes:
It was one space to the left, not sure if I'm explaining that right.
Sent from my S10 using my thumbs, with tapatalk.
How did you copy? Did you use the small icon in the top right corner? When you move the cursor on it, it shows "Copy Contents".
Yup,
I will play around and see, seems as though it should work from your reply.
I could be messing it up.
Sent from my S10 using my thumbs, with tapatalk.
Hi,
so i dont mess all this up, to change duck dns to my other dns.
i know i need to change the config.php in nextcloud.
where do i find line 38 ( - URL=xxxx.de #insert your domain name - yourdomain.url) from the yml file?
thanks
Whereever you created the docker-compose.yml
k thanks, i thought that was like a temp file used for creating the nextcloud container.
Its a template for setting up the container. When you modify it and again use the docker-compose up -d the container is recreated.
i hate this, i changed to my url
docker logs -f letsencrypt shows server ready.
i changed the url in nextcloud config
changed the yml file.
i get a 502 error on the page.
went into docker and my letsencrypt docker was no longer showing me the ports, so i edited the docker image directly ( i hate doing that).
still 502 error.
my fear is if i keep running docker logs -f letsencrypt, i'll have my cert bannned for a week. this already happened trying to setup before.
so i know it's a config issue, where can i look in cli to figure it out?
where else would there be an issue?
oh, what started all this thread was a i changed my routers to google wifi (big mistake no ddns) a few months ago, i had no time to setup everything at the time. so with life back to normal, i'm trying to setup everything back up.
so i found a container called blaize/docker-dynamic-dns.
read the guide and set it up as per the guide.
Unable to run docker-compose up -d, folder name conflicts, so it trys to recreate the whole setup.
what the best way to edit the container info without using docker?
would it be in,
/var/lib/docker/containers/873655a0cc3422ecfeb1328965e55e9f0bc7686111461a9f27a15d0d71fe857
then editing the json file?
Its a template for setting up the container. When you modify it and again use the docker-compose up -d the container is recreated.
so re running docker-compose up -d
will not cause corruption in the setup?
my fear is if i keep running docker logs -f letsencrypt, i'll have my cert bannned for a week.
this command only shows you the logfile of the docker container...
Did you restart your containers after changing the configs?
will not cause corruption in the setup?
no, thats the beauty of docker-compose.
so re running docker-compose up -d
will not cause corruption in the setup?
If nothing changed, nothing happens.
If something changed, the docker will be recreated with the new settings.
Alles anzeigenthis command only shows you the logfile of the docker container...
ok
Did you restart your containers after changing the configs?
yes
no, thats the beauty of docker-compose.
i get an error running docker-compose up -d
ERROR: for letsencrypt Cannot create container for service letsencrypt: Conflict. The container name "/Letsencrypt" is already in use by container "735b534f76e4295a513d189b1cda
<span style="background-color: rgb(0, 0, 0);">bed82b64c86e2b5b7a409890f317ea7b472d". You have to remove (or rename) that container to be able to reuse that name.
@HackitZ where exactly is "north of the border"?
Canada.
think i'll just start all over.
my only unknown is did i setup blaize/docker-dynamic-dns properly. config seems pretty simple but i dont know.
So if I run the docker-compose again.
I'll be reinstalling letsencrypt, can I just import my letsencrypt keys from the old install?
This way I'm not jeopardizing letsencrypt blocking me.
Sent from my S10 using my thumbs, with tapatalk.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!