Yes. Is there something wrong with it ?
PS/ Solved. I had put the command the other way around after reinstall. Stupid me
Yes. Is there something wrong with it ?
PS/ Solved. I had put the command the other way around after reinstall. Stupid me
I did a complete clean install and it still returns the same:
docker create network my-net
Unable to find image 'network:latest' locally
Error response from daemon: pull access denied for network, repository does not exist or may require 'docker login'
Anyone else facing this issue ? Anyone has an idea on how to solve this ?
I am confused by your question: if the drive is there to make a back up, why would you access it as you would do it for a sharedfolders ?
I have my back up drive formatted as ext4 as the USBbackup plugin - unless mistaken - does not work well with other partition types.
Cheers geaves.
No, thanks for your support Very much appreciated.
I will do a clean install and I will see from there.
Have a nice afternoon/evening.
I tried all these lines again and nothing different.
I am wondering if I should not make a clean install and start again from there. Maybe something went wrong when I upgraded from OMV3 to 4. What do you think ? Is clean install the likely way to get rid of this when everything else was tested ?
Thanks. I did it the brute way, removing manually all configuration files, uninstalling and reinstalling but still no result.
I therefore conclude that the problem might be anywhere else than in docker.
Any idea ?
Could it be a configuration file missing somewhere ? Has anyone faced this issue also ? Is there a way to create the network:latest image ?
Many thanks
Sigh ... I did it through the GUI and same thing again. I am good to reinstall everything without any issue solving.
I do not really see what else I can try.
EDIT: could someone post its /etc/default/docker file ? Mine is empty
Exactly If i manage to confuse you for a second, then that's already an achievement
I did the process above and still no result. When I did, docker was already uninstalled after step 3 and docker-ce was still enabled in the web GUI. Also, I never lost any data from the containers (I would have assumed that I would have lost everything after configuration reset :s)
PS: It is set as static
EDIT: I stopped the docker service and did the process again but same result
Attached is the output. To remove docker, I did:
apt-get purge openmediavault-docker-gui
apt-get purge docker-ce
apt-get -f install
EDIT: I did the whole process once more. Now it does not want even to add the network with docker network create --driver bridge my-net
////
regarding the router, I hope I did it right. I also attached the current settings.
Thanks geaves - you are the white knight in my OMV legacy
I am willing to solve the docker issue but where can I start ? I did a apt-get purge when de-installing and de-activated the repo; before reactivating docker-ce and reinstalling the whole package. Any idea ?
EDIT/ for duckdns, I followed these steps. I checked again the settings and they are correct :s So there is something else. Port forwarding ?
I managed to create the network with docker network create --driver bridge my-net. But is it the same result ?
When I do docker logs -f letsencrypt, I get the following error:
Failed authorization procedure. duckdns.org (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://duckdns.org/.well-known…_c5dRPCZn9unSLkz3Wcj_4So: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>"
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: duckdns.org
Type: unauthorized
Detail: Invalid response from
http://duckdns.org/.well-known…_c5dRPCZn9unSLkz3Wcj_4So:
"<html>\r\n<head><title>404 Not Found</title></head>\r\n<body
bgcolor=\"white\">\r\n<center><h1>404 Not
Found</h1></center>\r\n<hr><center>"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container.
I think I made the port forwarding correct. There is just one thing I am not sure I understand from the video, technodad refers to the letsencrypt internal addresse at around 7:34. Is it different from the internal ip address of the server ? I can only change the last three digits in my router configuration ...
So I tried reinstalling docker removing the repo docker-ce via the command line, but I still have the same error.
docker network ls gives:
NETWORK ID NAME DRIVER SCOPE
57a1da62b727 bridge bridge local
670cd0e97e70 host host local
8a9dbc8fbf47 none null local
EDIT: I also tried to log in to docker, but that did not change a thing
Hi,
I followed the video from technodad to install letsencrypt but i have an issue when i try to create a new network in docker:
# create network my-net
Unable to find image 'network:latest' locally
Error response from daemon: pull access denied for network, repository does not exist or may require 'docker login'
Can somebody please help me with that ?
Solved by putting the container in bridge mode. Thank you
Thanks guys. I made the switch. All went well and now I understand what geaves was talking about
I will reconfigure and try to solve the openvpn/transmission issue. I will let you know if there is any more troube.
Have a nice day !
Thanks. I am on OMV3 so that explains why then. Should I upgrade to OMV4 for this or is is still fine to refer to /srv/[disk] instead ?
For me, sharedfolders was not there and I created it when I was following the tutorials. Still my shared folders do not show there. So what I need to find is a way to get that redirect going on.
Gotcha. So what is missing in my case is the redirect. I will dig into this.
Sure, enjoy your weekend