-
|
This menu item will launch all the apps using the configured .env file and the docker-compose.yml file (Docker must be already installed and running)
All Apps started you can visit the web dashboard on http://localhost:8081/ . If not already done use the previously generated earnapp node URL to add your device in your earnapp dashboard. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 14 replies
-
|
Hello and thanks to reaching out to me, your feedback is very important. Please, could you one a powershell and issue this command: |
Beta Was this translation helpful? Give feedback.
-
|
Hello ty for your reply, i am on windows10 pro 64 bit 21h2 . attached is a screenshot, docker on showing in the background with no program loaded.
Windows PowerShell Try the new cross-platform PowerShell https://aka.ms/pscore6 PS C:\Users\VALKYRIE> docker ps
PS C:\Users\VALKYRIE> TY for your help. i followed you on your videos i hope we can get this running and start making so dough |
Beta Was this translation helpful? Give feedback.
-
|
PowerShell 7.3.0 Still same thing. |
Beta Was this translation helpful? Give feedback.
-
|
Trying this resolution: https://forums.docker.com/t/the-term-docker-is-not-recognized-as-the-name-of-a-cmdlet-function-script-file-or-operable-program/107415 |
Beta Was this translation helpful? Give feedback.
-
|
back to step 4 on runme.ps1.... (hyper V is turned back off because of above thread) |
Beta Was this translation helpful? Give feedback.
-
the project seems to work fine, it's the docker installation that is behaving strangely. Also the error you had initially (also the second one) depends on the docker installation not the project setup. Did you do the manual docker install or the automatic one provided in the project script? |
Beta Was this translation helpful? Give feedback.
-
just an heads up about this: be careful, it fix this docker installation issue regarding commands not runnig caused by the docker PATH variable not being added to system variables, but the linked solution is for windows server. It may use (and often uses in many guides) a different than the standard docker installation system which while it shouldn't prevent the use of this project or other docker containers, can cause some strange behavior on windows home or pro. Better to install docker following the directions on the official docker site or use the unattended installation provided in the project with the script that automates the standard installation of docker desktop. |
Beta Was this translation helpful? Give feedback.
-
|
I believe i am resolved: |
Beta Was this translation helpful? Give feedback.
-
there you are just running the bitping setup container. the steps to use this project are to setup the env file and then run the stack. in docker desktop you will then see all the containers gathered in a dropdown menu. |
Beta Was this translation helpful? Give feedback.
-
|
automatic. now i have had to do a reboot and i lost the container. so now i
have to add it again.
…On Sun, Nov 20, 2022 at 2:06 PM MRColor ***@***.***> wrote:
Trying this resolution:
https://forums.docker.com/t/the-term-docker-is-not-recognized-as-the-name-of-a-cmdlet-function-script-file-or-operable-program/107415
just an heads up about this: be careful, the linked solution is for
windows server. It may use (and often uses in many guides) a different than
the standard docker installation system which while it shouldn't prevent
the use of this project or other docker containers can cause some strange
behavior on windows home or pro. Better to install docker following the
directions on the official docker site or use the unattended installation
provided in the project with the script that automates the standard
installation of desktop docker.
—
Reply to this email directly, view it on GitHub
<#11 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4JFJUKBCU7QGPB5CVHT26DWJJZDDANCNFSM6AAAAAASFSRJMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
that container is ephemeral and it is fine that it disappears. is launched during the setup of the env file. the complete stack is composed of multiples containers |
Beta Was this translation helpful? Give feedback.
-
|
how did you install docker ? I think your docker installation is incomplete or corrupted. Try uninstalling docker and reinstalling using option 2 in the menu or following the instructions on the docker desktop site. |
Beta Was this translation helpful? Give feedback.
-
|
doing now. |
Beta Was this translation helpful? Give feedback.
-
|
Can you tell me if I need to enable Hyper V? the above forum I saw convinced me to turn off this feature, I'm curious if you think I need to enable? |
Beta Was this translation helpful? Give feedback.
-
|
hyper-v is not needed to use docker. Just enable virtualization platform and wsl features. Also install wsl update package or use the wsl on the Microsoft store. |
Beta Was this translation helpful? Give feedback.
-
|
ok reinstalled with auto step 2. |
Beta Was this translation helpful? Give feedback.
-
|
this is what i get from running option 4: This menu item will launch all the apps using the configured .env file and the docker-compose.yml file (Docker must be already installed and running)
what do i do? |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the info, i'll look into this now |
Beta Was this translation helpful? Give feedback.
-
|
it's related to the docker credentials. This is a docker feature not used in this project as all files and images used could be downloaded from docker default register without authentication. The simplest solution to attempt is to try to reboot your machine to force your account informations and credentials to refresh, and then start the stack again opening a powershell in the project root folder and using Edit: if this is not enough look to this post https://forums.docker.com/t/docker-credential-desktop-exe-executable-file-not-found-in-path-using-wsl2/100225/30 that explains why this happens (e.g. in case like: had a bad docker installation then removed it but leftovers config files are causing problems with the new correct installation). In a nutshell the docker config file is not correct due to an old bad docker installation that left some residue after uninstall, docker tries to read and use some credentials that don't exist for downloading the requested images. You can proceed to eliminate this incorrect configuration by deleting the following portion from the docker configuration file (be careful to keep the indentation and the right parentheses:
|
Beta Was this translation helpful? Give feedback.
-
|
In a nutshell the docker config file is not correct due to an old bad docker installation that left some residue after uninstall, docker tries to read and use some credentials that don't exist for downloading the requested images.
|
Beta Was this translation helpful? Give feedback.
In a nutshell the docker config file is not correct due to an old bad docker installation that left some residue after uninstall, docker tries to read and use some credentials that don't exist for downloading the requested images.
Fix you could try:
{ "auths": { "docker.your.domain.": { "auth": "badcredentials1234=" } } }from the file, this fix the issue if it's caused by a previous bad docker installation or misconfiguration