I tried to download spleeter on my mac m1 version, but it keeps to occur errors everytime no matter what method I use.
Using pip :
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> numpy
Using docker:
WARNING: The requested image's platform (linux/amd64) does not match the detected
host platform (linux/arm64/v8) and no specific platform was requested
docker: Error response from daemon: failed to create shim task: OCI runtime
create failed: runc create failed: unable to start container process: error during
container init: error mounting "/host_mnt/Users/ghboo/output" to rootfs at "/output":
mount /host_mnt/Users/ghboo/output:/output (via /proc/self/fd/14), flags: 0x5000:
not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.
I think spleeter's docker image doesn't support for m1 chip
https://github.com/deezer/spleeter/issues/696
Anything doesn't let me run spleeter. Please help.
Related
I am having trouble with docker, i had an image which i imported using the following command:
docker image import C:\Users\****\Downloads\imagename-b1.tar imagename-b1:latest
And when i try to run image/container, for the image it gives this error:
Failed to run image. Error invoking remote method 'docker-run-container': Error: (HTTP code 400) unexpected - No command specified
And for the container it gives this error:
Error invoking remote method 'docker-start-container': Error: (HTTP code 400) unexpected - failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--name": executable file not found in $PATH: unknown
Docker Version 20.10.21, build baeda1f
I'll appreciate any suggestion.
Thank you
Just had a similar issue.
Try starting the image from your terminal. Works for me when I did that.
Can check this Github issue too.
https://github.com/dotnet-architecture/eShopOnContainers/issues/1699
After using the CMD to start the image, later encountered port issues.
Found this solution that works now. https://github.com/docker/for-win/issues/9272#issuecomment-776225866
TL;DR:
net stop winnat
Then start your docker container. Then
net start winnat
I'm following https://develop.kde.org/docs/kirigami/introduction-getting_started/#mainqml (kirigami introduction) to create apps for my pinephone (arch64v8). I'm using KDevelop and have an aarch64 docker container with Arch ARM, which I want to use as a build host.
KDevelop finds the container, but building fails after:
docker: Error response from daemon: failed to create shim: OCI runtime create failed:
runc create failed: unable to start container process: exec: "/usr/bin/cmake": stat
/usr/bin/cmake: no such file or directory: unknown.
cmake is in /usr/sbin/, not /usr/bin.
I tried changing the cmake location in KDevelop's global CMake configuration, but that didn't help.
I could cymlink cmake in the container, but that's hard to maintain.
How do I tell KDevelop where to find cmake in the container?
Apparently, the solution was to remove the ,kdev4 file and reopen the project. Then you get a chance to say where the cmake is.
An attempt to install Cygwin in an Docker container on Windows fails with the error:
re-exec error: exit status 1: output: time="2020-12-11T15:00:26+01:00" level=error msg="hcsshim::ImportLayer - failed failed in Win32: The system cannot find the path specified. (0x3)" error="hcsshim::ImportLayer - failed failed in Win32: The system cannot find the path specified. (0x3)" importFolderPath="D:\\docker\\tmp\\hcs678884955" path="\\\\?\\D:\\docker\\windowsfilter\\9b956fcbc6cf19ba2f18fe39e12639da939e14916f019a32541df16e7dbf5b1e"
hcsshim::ImportLayer - failed failed in Win32: The system cannot find the path specified. (0x3)
At https://github.com/microsoft/hcsshim/issues/835, they write that hardlinks are the reason for the problem. Zipping/unzipping the CygWin folder should help fix it but, using Cygwin installer, you have no control over the unattended installation.
Is there any other method for how Cygwin can be installed in a Docker container?
Is it possible to suppress the creation of hardlinks by Cygwin installer?
This is caused by the fact that cygwin is using hard links that seems cause docker to fail, try to install cygwin locally, then zip & unzip into the separate folder, they simply add cygwin using ADD
I have already implemented my .bna file named "supply-chain-network" but I think that the problem isn't in the .bna, since I have tried with another .bna(the basic-sample-network in hyperledger composer playground) and the problem still persists.
Composer version: 0.19.2
Operating System: Ubuntu 16.04 running in VM
Steps:
download the fabric-dev-servers
./downloadFabric.sh
./startFabric.sh
./createPeerAdminCard.sh
exported the basic-sample-network from the playground (my-basic-sample.bna)
composer network install --card PeerAdmin#hlfv1 --archiveFile my-basic-sample.bna#
composer network start --networkName my-basic-sample --networkVersion 0.0.1 --networkAdmin admin --networkAdminEnrollSecret adminpw --card PeerAdmin#hlfv1 --file networkadmin.card
And I got the following error:
Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: 2 UNKNOWN: chaincode error (status: 500, message: cannot get package for chaincode (my-basic-sample:0.0.1))
I have checked and the name of the network and the version by issue the command:
composer archive list -a my-basic-sample.bna
And I got:
Listing Business Network Archive from my-basic-sample.bna
Identifier:my-basic-sample#0.2.4-deploy.0
Name:my-basic-sample
Version:0.2.4-deploy.0
Command succeeded
I have tried to issue composer network start with version 0.2.4 instead of 0.0.1 and I got the same error.
The log of the docker by typing:
docker logs peer0.org1.example.com
I got:
I have seen on https://github.com/hyperledger/composer/issues/3591#issuecomment-386718739 that this error is caused by an extra character when copy pasting the command from the hyperledger composer website. I have done what hi2rashid suggests(copy the command to a notepad and then copy to the command line) but I still got the same error.
Anybody know how to fix this ?
You are very close to getting this working ...
The composer archive list command has listed the version as "0.2.4-deploy.0" - although this doesn't look like a version "number" it is. Your network start command should include --networkVersion 0.2.4-deploy.0
This long version comes from Composer Playground autogenerating versions when the model is upgraded.
I am looking for a way to run vagrant inside docker container. I tried using Ubuntu base container but had faced some issues while doing vagrant up, it failed.
root#991baf290ddc:/srv# vagrant up
VirtualBox is complaining that the installation is incomplete. Please
run VBoxManage --version to see the error message which should contain
instructions on how to fix this error.
root#991baf290ddc:/srv# VBoxManage --version
WARNING: The character device /dev/vboxdrv does not exist. Please install the virtualbox-dkms package and the appropriate headers, most likely linux-headers-.
You will not be able to start VMs until this problem is fixed.
5.0.40_Ubuntur115130
I tried installing virtualbox-dkms package but no help.
Deleting module version: 5.0.40 completely from the DKMS tree.
Done.
Loading new virtualbox-5.0.40 DKMS files...
dpkg: warning: version '*-*' has bad syntax: version number does not start with digit
dpkg: warning: version '3.10.0-514.16.1.el7.x86_64' has bad syntax: invalid character in revision number
It is likely that 3.10.0-514.16.1.el7.x86_64 belongs to a chroot's host
Building only for *
Building initial module for *
: using /lib/modules/4.4.0-83-generic/build/.config
(I hope this is the correct config for this kernel)
Done.
Error! The directory /lib/modules/* doesn't exist.
You cannot install a module onto a non-existant kernel.
The command '/bin/sh -c dpkg-reconfigure virtualbox-dkms' returned a non-zero code: 6
[root#test-docker vagrant-in-docker]#