What is benefit of install annaconda over docker.
For python/pytorch programming. I installed annaconda docker image on Ubunut 20.4
But found many problems need to solve such as Display on opencv2 (already solved). and spyder error on libgl.so.1 cannot found and still no idea how to solve.
So, how about just install annacona on Ubuntu host. Becuase it should working as smoothly well on my job.
Related
I'm trying to setup Frigate in a Docker container running on Ubuntu 22.04 on my Beelink. To do so you need have some prerequisites.
Docker
MQTT
And more
I've installed Mosquitto MQTT before on a Raspberry Pi running Ubuntu 22.04 and it worked. After trying to install it again on my Beelink running Ubuntu, it gave the error seen in the screenshot.
Any advice?
I've uninstalled it and reinstalled it. This is all new to me. Just started using Linux and the terminal.
Apologies for not attaching the screenshots earlier. I don't have access to the actual text right now. I'll be sure to add text next time instead of a screenshot.
enter image description here
I am watching a course on Hyperledger Composer development online. I installed all the required prerequisites, docker, docker-compose, nodejs, golang. After cloning the fabric-samples repository from github. There is a file called byfn.sh inside a folder called first-network. On running the command ./byfn.sh up, it's giving the following error:
If, someone has experience working on it, please help. Any help would be appreciated. Thank you.
I think the first thing you should do is stop looking at or trying to use Hyperledger Composer. It is end of life now and some of it's components will have problems even if you install the exact required versions (for example the rest server fails to launch now on node 8 but changing to a newer version of node may break other parts of Composer).
As you had planned to use it with hyperledger fabric I would suggest that you just invest your time in Hyperledger fabric, see https://hyperledger-fabric.readthedocs.io/en/latest/
Regarding your problem with docker, I suspect you tried to install docker through the apt command in your wsl window ? I'm guessing that you are using WSL2, but if you are using WSL1 then docker will never work in a WSL1 environment. If it was WSL2 then the docker daemon doesn't automatically start in that environment you need to start it yourself first. I think the command is service docker start. The important thing here is to make sure you are using WSL2 and not WSL1 (see hyperledger fabric link later which provides guidance on making sure you are using WSL2).
An alternative to installing docker into WSL2 directly would be to install Docker Desktop for Windows and follow the hyperledger fabric instructions here https://hyperledger-fabric.readthedocs.io/en/latest/prereqs.html#wsl2
So we downloaded this docker image that we need to run on the machines of me and a friend. I am on a mac and he is on a linux box. We are not techie people so please forgive this naive question :)
When running the docker using docker build -t app-name/site.com . we were running into some very cryptic G++ errors which sent us on a wild goose chase and a vicious circle of googling and debugging. In the end we figured out that my friend's machine was Linux 18.04, but in the Dockerfile it said FROM ubuntu:16.04. So when we updated this to FROM ubuntu:18.04 his docker build was successful and he was able to launch the app.
So now we are trying to figure out how to get this running in my mac. Does anyone know what update we should do to this line to get it running in mac? I am running macOS Catalina.
Any help is much appreciated!
Docker is originally developed for Linux community. Then it is ok for Mac.
Here is one example of how to make your mac get a Linux container. Run this
docker pull ubuntu
This means you are able to construct a Ubuntu env on your mac machine.
FYI, you can release your docker image on docker's website then fetch it on your mac.
Refer to: https://ropenscilabs.github.io/r-docker-tutorial/04-Dockerhub.html
I'm brand new to Stack Overflow and the world of containers, so hopefully my questions aren't too silly.
So first I will say that I'm aware that there are other questions similar to the one I'm asking, but I've tried the solutions in all of the ones I've found and they haven't worked for me. If there is another question out there that does have the answer, I'm really sorry for double-asking!
So, background info: I've got a Raspberry Pi 3 running Raspbian, with docker freshly installed. I'm able to pull images down from repositories with no real issues. However, I can't run any of them. I always get the same error (the title of my question). Someone pointed out that it might be because there are mostly 64-bit images in the repositories and I'm running a 32-bit machine, which I thought was the problem. but then I pulled a 32-bit Debian image (the first thing I could find that was 32-bit) and tried to do docker run with the image ID. but it still comes up with that error.
What else may cause that error? Or maybe it's the fact that I'm doing it on a Pi...? Open to anything!
Thanks in advance!
I have had similar issues when I tried to run Docker images on Rasperri Pi. Most of the Docker images are built for x86/x64 architecture. You need Docker-based apps packaged specifically for ARM to run on Raspberry Pi. Hypriot (Based on Debian) is one of the Raspberry Pi images that built for running latest Docker. Check it out here. They also have images specifically built for ARM. Search for hypriot on docker hub.You still may run these images with your current Docker installation, which I did not try.
This morning I've started playing with Docker, so installed boot2docker on my Mac.
All seemed to be going well, following the Working with Docker Images documentation until I tried to create a Dockerfile to install the ruby gems.
I spent a long time banging my head against the wall as to why it couldn't connect to install the gems... then I eventually worked it out, so adding this here in case anyone else has this problem in future, as there wasn't anything on Google about it.
Turns out that, because my internet bombed out during the apt-get update command, it didn't complete the update, however running it again, docker was using the cached (incomplete) data, and so if didn't work.
The fix... Run the docker build without the cache using the command...
docker build -no-cache --tag="<vendor>/<build>:<tag>" .