I am trying to setup a docker image for work, but I am running into issues with libssl1.0.0. When I run docker-compose build, this is the output I get back
---> Running in 1d506ae8e916
dpkg: regarding libssl1.0.0_1.0.1t-1+deb8u11_amd64.deb containing libssl1.0.0:amd64, pre-dependency problem:
libssl1.0.0 pre-depends on multiarch-support
multiarch-support is not installed.
dpkg: error processing archive libssl1.0.0_1.0.1t-1+deb8u11_amd64.deb (--install):
pre-dependency problem - not installing libssl1.0.0:amd64
Selecting previously unselected package libssl1.0.0:amd64.
Errors were encountered while processing:
libssl1.0.0_1.0.1t-1+deb8u11_amd64.deb
ERROR: Service 'app' failed to build: The command '/bin/sh -c dpkg -i libssl1.0.0_1.0.1t-1+deb8u11_amd64.deb' returned a non-zero code:
I have mutliarch-support installed, I even sudo apt-get remove multiarch-support and reinstalled it. Same with libssl1.0.0, I even removed libssl1.1.0.
You need the package in your image not in your host. Install multiarch-support in one previous RUN command than the one that gives the error.
Related
Guys while i was running anchor test on macbook m1, i am getting this error. Does anybody have a fix for this.
BPF SDK: /Users/dhruvjain/solana/bin/sdk/bpf
Running: rustup toolchain list -v
Running: cargo +bpf build --target bpfel-unknown-unknown --release
error: failed to download `solana-frozen-abi v1.9.9`
Caused by:
unable to get packages from source
Caused by:
failed to parse manifest at `/Users/dhruvjain/.cargo/registry/src/github.com-1ecc6299db9ec823/solana-frozen-abi-1.9.9/Cargo.toml`
Caused by:
feature `edition2021` is required
consider adding `cargo-features = ["edition2021"]` to the manifest
I found that i may have old rust or cargo version. But they seem to be up to date.
rustc 1.59.0 (9d1b2106e 2022-02-23)
Cargo Version
cargo 1.59.0 (49d8809dc 2022-02-10)
I ran cargo clean but i still got the same error. Can somebody help me to solve this issue.
what solana version ?
solana -V
Ensure you are runnning 1.9.9
sh -c "$(curl -sSfL https://release.solana.com/v1.9.9/install)"
I want to create a Docker image in big sur (M1 chip) with the help of visual studio, but I get the following error :
Starting: "docker" exec -i 737ff06a8ab3 /bin/sh -c "ID=.; if [ -e /etc/os-release ]; then . /etc/os-release; fi; if [ $ID = alpine ] && [ -e /remote_debugger/linux-musl-x64/vsdbg ]; then VSDBGPATH=/remote_debugger/linux-musl-x64; else VSDBGPATH=/remote_debugger; fi; $VSDBGPATH/vsdbg --interpreter=vscode --interpreter=vscode"
Error from pipe program 'docker': qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
The first time it works correctly, but the second time the error occurs
how to resolve it
I ran into this issue when my Dockerfile specified a generic image name but installed linux/amd64 software. What occurs in this instance is that you will get an ARM64 (M1) base image (unless you specify a different --platform in your build call), which does not come pre-populated with x86 shared objects.
It will faithfully try to run the x86 (amd64) code through Docker's qemu hypervisor but discover it is missing some basic shared objects that must be architecture-specific.
What this means is that you need to call up your OS package manager and install the x86 shared object packages and make sure they are in your LD_LIBRARY_PATH. The error messages you see will tell you what you need to find.
In my case, using an arm64 image based on ubuntu/debian, I use the 'apt' package manager. In other OS's, you might use 'yum' or 'rpm'. Go to the web site for that OS (e.g. packages.debian.org) and search for your library dependencies in their packages, then specify that in your RUN call to build into the image.
For your error, you are likely looking for 'libc6'. Here's how I loaded it, which is an amd64 cross-compile package:
Example Dockerfile entries:
RUN apt-get update
RUN apt-get install -y wget unzip
RUN apt-get install -y libc6-amd64-cross
RUN ln -s /usr/x86_64-linux-gnu/lib64/ /lib64
ENV LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/lib64:/usr/x86_64-linux-gnu/lib"
There may be other libraries you find missing, so you just have to step through it and resolve the missing shared objects.
I'm trying to download docker on my raspberry pi 4 but I keep getting the same error.
The error message I get is:
W: https://deb.nodesource.com/node_14.x/dists/buster/InRelease: No system certificates available. Try installing ca-certificates.
W: https://deb.nodesource.com/node_14.x/dists/buster/Release: No system certificates available. Try installing ca-certificates.
E: The repository 'https://deb.nodesource.com/node_14.x buster Release' no longer has a Release file.
I don't understand this because I've re-installed ca-certificate but that still doesn't fix it.
(Note: I don't know if this means anything but I also get the same error when I run sudo apt update)
Okay I fixed the problem by simple running sudo apt-get install --reinstall ca-certificates
I tried to build HandTrackingExample and get this error
ERROR:
/Users/air/Documents/mediapipe/mediapipe/examples/ios/handtrackinggpu/BUILD:34:16:
ProcessEntitlementsFiles
mediapipe/examples/ios/handtrackinggpu/HandTrackingGpuApp_entitlements.entitlements
failed (Exit 1): plisttool failed: error executing command
bazel-out/host/bin/external/build_bazel_rules_apple/tools/plisttool/plisttool
... (remaining 1 argument(s) skipped)
Note: The failure of target
#build_bazel_rules_apple//tools/plisttool:plisttool (with exit code 1)
may have been caused by the fact that it is running under Python 2
instead of Python 3. Examine the error to determine if that appears to
be the problem. Since this target is built in the host configuration,
the only way to change its version is to set --host_force_python=PY3,
which affects the entire build.
If this error started occurring in Bazel 0.27 and later, it may be
because the Python toolchain now enforces that targets analyzed as PY2
and PY3 run under a Python 2 and Python 3 interpreter, respectively.
See https://github.com/bazelbuild/bazel/issues/7899 for more
information.
I tried build with --host_force_python=PY3 and PY2 but error the same
The link that is given in the error did not find a solution to your problem. How do I build a project correctly?
Try it
$ brew install python
$ sudo ln -s -f /usr/local/bin/python3.7 /usr/local/bin/python
$ python --version
Python 3.7.4
$ pip3 install --user six
I am trying to install opencv using conda on a windows machine. I am running the following command:
conda install --channel https://conda.anaconda.org/menpo opencv
and getting the following error:
Solving environment: done
## Package Plan ##
environment location: C:\ProgramData\Anaconda2
added / updated specs:
- opencv
The following NEW packages will be INSTALLED:
opencv: 2.4.11-py27_1 menpo
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: - WARNING conda.gateways.disk:exp_backoff_fn(49):
Uncaught backoff with errno EEXIST 17
failed
ERROR conda.core.link:_execute(502): An error occurred while installing
package 'None'.
IOError(13, 'Permission denied')
Attempting to roll back.
Rolling back transaction: done
IOError(13, 'Permission denied')
WindowsError(183, 'Cannot create a file when that file already exists')
Other people seem to have similar problems (https://github.com/conda/conda/issues/4393). One of the solutions I found was to downgrade conda. I am currently using conda 4.5.4 and when I try to downgrade using conda install conda=4.2 I get the following error:
The following packages will be DOWNGRADED:
conda: 4.5.4-py27_0 --> 4.2.16-py27_0
conda-build: 3.10.5-py27_0 --> 3.9.2-py27_0
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: failed
ERROR conda.core.link:_execute(502): An error occurred while uninstalling
package 'defaults::conda-build-3.10.5-py27_0'.
WindowsError(5, 'Access is denied')
Attempting to roll back.
Rolling back transaction: done
WindowsError(5, 'Access is denied')
Regarding this issue I found the following similar posts:
conda update conda permission error
Anaconda : Update conda failed because permission error
But the solutions given do not fix my problem.
I also had a problem with installation and usage of the OpenCV library. If you have such а problem, you can try:
uninstall opencv with: conda remove --yes opencv (in case you have an installation but it does not work properly)
install OpenCV through pip: pip install opencv-python
I think this is a problem with opencv that comes from Anaconda channels. I came across this problem four months ago. Тhe problem may be resolved right now.
My guess is that you did not run this command with administrator privileges！