I have installed Processor-SDK-AM57x on Ubuntu 18.04 linux distribution and build my project successfully.
I have to create build environment on Docker image and build my application inside contianer.
how can I install my dependencies Processor-SDK-AM57x on Ubuntu 18.04.
do I need to include a texas instruments key into the trusted keys of you Docker-Container, if yes how?
any help in this regard would be appriciated!
Thanks
Related
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
While attempting to install, in VS Code, the Fabric samples and binaries through the curl command :
I've encountered the following error, as soon as Fabric docker images are pulled :
The command 'docker' could not be found in this WSL1 distro. We recommend to convert this distro into
WSL 2 and activate the WSL integration in Docker Desktop settings.
N.B: Docker version 20.10.0-beta1
Thus any relevant feedback, not impacting the usage of the IBM Blockchain Platform v.1.0.39 (e.g. prerequisites installed), would highly be appreciated.
Best
See the Docker Desktop WSL 2 backend guide.
Specifically, you need to convert your Ubuntu distribution to WSL2 (it is currently WSL1). To do so, see Step 6 in the Install section:
To upgrade your existing Linux distro to v2, run:
wsl.exe --set-version Ubuntu 2
Either that, or create a new WSL instance by backing up the WSL1 version (wsl --export) and then importing it into a new copy (wsl --import). See wsl --help for the parameters needed.
Then proceed with the rest of the Docker installation instructions.
in my case, resolved by enabling the WSL2 distro option in the docker settings.
As the log says (in your qusetion)
We recommend to convert this distro into WSL 2 and activate the WSL integration in Docker Desktop settings.
in Docker Settings
go Resources
go WSL INTEGRATION
check Enable integration with my default WSL distro
Apply & Restart
I faced the same issue and solved it by navigating to: docker desktop > Resources > wsl integration then choose the right distro for integrating docker with.
I took an older macbook back in use. It previously had boot2docker installed when the native docker for mac didn't exist yet. That might be the root cause of my issue.
I've installed the new docker for mac but when I run docker-compose I've got the following error:
docker.errors.TLSParameterError: Path to a certificate and key files must be provided through the client_config param. TLS configurations should map the Docker CLI client configurations. See https://docs.docker.com/engine/articles/https/ for API details.
I don't want to install a docker machine with virtual box or anything. I just want to run it natively like a fresh docker for mac installation. All the solutions I've found so far require me to use a docker-machine.
Fixed it by unsetting all legacy docker machine environment variables so that it uses the correct docker commands
unset ${!DOCKER_*}
I've found the solution on the docker troubleshooting page over here.
This was a huge surprise for me:
Today, using Docker For Mac (18.03.1-ce-mac65), I ran a Debian Stretch image. Inside the image I mounted the latest Raspbian Stretch image (2018-04-18-raspbian-stretch-lite) using mount. I then used chroot to this mounted Raspbian filesystem.
This is where it got weird. I was able to use apt (without any special modifications) to install software into this mounted filesystem.
Running:
dpkg --print-architecture
returned: armfh
and the software I installed (vim) worked like a charm
I was even able to compile a simple program using gcc and run it.
But, I need to know! How is this possible?
According to Docker:
Docker for Mac provides binfmt_misc multi architecture support, so you can run containers for different Linux architectures, such as arm, mips, ppc64le, and even s390x.
EDIT
On Linux, you can install qemu-user-static and then follow this git repo to get cross-architecture support!
I have downloaded docker binary version 1.8.2 and copied that to my backup server (centos server) which doesn't have internet connectivity. I have marked this as executable and started the docker daemon as mentioned in [https://docs.docker.com/engine/installation/binaries/][1]. But it doesn't seem to get installed as a docker service. For all the commands, I have to execute as sudo ./docker-1.8.2 {command}. Is there a way to install docker-engine as a service? Currently sudo docker version shows command not found. I'm a newbie to docker setup. Please advise.
Why not download the rpm package (there are also centos 6 packages), copy to USB stick and then to your server and simply install it with rpm command and that's it. That way you'd get the same installation as if you were to run yum.
Of course you may have some dependencies missing, but you could download all of these as well.
Firstly, if you're downloading bare binaries on an enterprise linux, you're probably doing things in a very bad way. Immediately, you're breaking updates and consistency, and leaving your system in a risky, messy state.
Try using yumdownloader --resolve to get the docker installable and anything it needs.
A better option may be to mirror the installation artifacts, and grab it from the local mirror, but that's beyond the scope if you don't do this already.