Docker image issue

Question

Docker image issue

mdzakirhussain opened this issue 5 years ago · 21 comments

Hello,

when I type in the terminal, the below shown

docker run -tiv pwd:pwd -w pwd --rm cloudv/fault:latest fault -V

I am getting the following error

docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:299: copying bootstrap data to pipe caused "write init-p: broken pipe"": unknown.

Answer 1 · 2019-11-22T10:03:09.000Z

Hi: That's usually indicative of the fact you're probably on Linux, using an older kernel than is supported by the Docker image.

Would recommend trying Ubuntu 18.04.

Answer 2 · 2019-11-22T10:15:26.000Z

Additionally, you can also update Docker to the latest possible version if you would like to keep your current operating system for the time being.

Please let me know how it goes.

Answer 3 · 2019-11-22T10:33:02.000Z

Hi: That's usually indicative of the fact you're probably on Linux, using an older kernel than is supported by the Docker image.

Would recommend trying Ubuntu 18.04.

Yes, I am using Ubuntu 18.04. Still facing the problem!!

Answer 4 · 2019-11-22T11:23:07.000Z

Alright, I'm going to need way more details.

Please show me the outputs of lsb_release -a and docker version.

Answer 5 · 2019-11-22T13:37:08.000Z

LSB Version: core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

dock version

Client:
Version: 18.09.9
API version: 1.39
Go version: go1.13.4
Git commit: 1752eb3
Built: Sat Nov 16 01:05:26 2019
OS/Arch: linux/amd64
Experimental: false

Server:
Engine:
Version: 18.09.9
API version: 1.39 (minimum version 1.12)
Go version: go1.13.4
Git commit: 9552f2b
Built: Sat Nov 16 01:07:48 2019
OS/Arch: linux/amd64
Experimental: false

Answer 6 · 2019-11-22T19:54:48.000Z

@Manarabdelaty Mind running docker version too?

Answer 7 · 2019-11-22T20:05:06.000Z

It prints the following:

Client: Docker Engine - Community
Version: 19.03.2
API version: 1.40
Go version: go1.12.8
Git commit: 6a30dfc
Built: Thu Aug 29 05:29:11 2019
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.2
API version: 1.40 (minimum version 1.12)
Go version: go1.12.8
Git commit: 6a30dfc
Built: Thu Aug 29 05:27:45 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.6
GitCommit: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
runc:
Version: 1.0.0-rc8
GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f
docker-init:
Version: 0.18.0
GitCommit: fec3683

Answer 8 · 2019-11-23T01:09:55.000Z

After several tries,now this is happening
when I type in the terminal> fault -V
I am getting this below shown

/usr/bin/fault: 7: [: -V: unexpected operator
Fault 0.2.0. ©Cloud V 2019. All rights reserved.

Answer 9 · 2019-11-24T08:43:29.000Z

Thank you!

First, I recommend updating Docker to the latest version using this guide: https://docs.docker.com/install/linux/docker-ce/ubuntu/

The second issue is a bug I have introduced by accident in the latest version and I will push a fix posthaste. I apologize.

Answer 10 · 2019-11-24T10:31:34.000Z

Alright, I think fixed the issue. Try now, please. 😅

Answer 11 · 2019-11-24T11:51:46.000Z

I am clueless what really happening ??? I personally feel, if there is one script file which may look-into auto installation of all the required things will possibly be the best solution.

Answer 12 · 2019-11-24T12:31:33.000Z

We're using Docker for that precise reason. Which, you can install from here: https://docs.docker.com/install/linux/docker-ce/ubuntu/ or by invoking this command: curl -fsSL https://get.docker.com | sh.

Docker runs a full environment with all dependencies preinstalled. It is like a virtual machine.

Answer 13 · 2019-11-24T13:37:19.000Z

After typing in the terminal, the following

docker run -tiv pwd:pwd -w pwd --rm cloudv/fault:latest fault -V

it then starts downloading something and finally gives this following error

docker: failed to register layer: symlink ../c6331cd098b1793002eb5bf2b9f52b5807c55f763fb145ca9a621f4f5aab2541/diff /var/lib/docker/overlay2/l/FWJD4SB3EEXD453WLUC5VLI3FL: no such file or directory.
See 'docker run --help'.

Answer 14 · 2019-11-24T13:38:41.000Z

If type the following in the terminal
fault -V
then I am getting this below error
/usr/bin/fault: 7: [: -V: unexpected operator
Fault 0.2.0. ©Cloud V 2019. All rights reserved.

Answer 15 · 2019-11-24T13:44:32.000Z

my request is

script file which installs all the following,( this script file user uses it and runs in the terminal )
A. docker
B. fault
C. any other that is part of the application

end-user should able to only type the commands related to fault-application to use it.

Answer 16 · 2019-11-24T13:59:30.000Z

My docker version
Docker version 19.03.5, build 633a0ea838
which is latest

Answer 17 · 2019-11-24T18:56:26.000Z

Given the variance in operating systems, a script file that installs everything and ensures functionality is nigh on impossible, given that even containerized approaches such as Docker are prone to misconfiguration errors on part of the end user. We do not have the resources to commit to such a feature. Docker is the tool we elected to bypass this problem and we stand by it.

When a docker is image is updated, you have to manually update it by typing docker pull cloudv/fault.

Please, once again try these commands specifically:

docker pull cloudv/fault:latest
docker run -tiv `pwd`:`pwd` -w `pwd` --rm cloudv/fault:latest fault -V

I have tested and found these commands to work just now on all of:

Apple macOS
Amazon Linux (our build server)
Lubuntu 18.04.

Answer 18 · 2019-11-25T08:20:48.000Z

Given the variance in operating systems, a script file that installs everything and ensures functionality is nigh on impossible, given that even containerized approaches such as Docker are prone to misconfiguration errors on part of the end user. We do not have the resources to commit to such a feature. Docker is the tool we elected to bypass this problem and we stand by it.

When a docker is image is updated, you have to manually update it by typing docker pull cloudv/fault.

Please, once again try these commands specifically:
docker pull cloudv/fault:latest
docker run -tiv `pwd`:`pwd` -w `pwd` --rm cloudv/fault:latest fault -V
I have tested and found these commands to work just now on all of:
* Apple macOS

* Amazon Linux (our build server)

* Lubuntu 18.04.

I am getting the following error
docker: Error response from daemon: invalid volume specification: '/:/': invalid mount config for type "bind": invalid specification: destination can't be '/'.
See 'docker run --help'.

Answer 19 · 2019-11-25T08:38:04.000Z

Given the variance in operating systems, a script file that installs everything and ensures functionality is nigh on impossible, given that even containerized approaches such as Docker are prone to misconfiguration errors on part of the end user. We do not have the resources to commit to such a feature. Docker is the tool we elected to bypass this problem and we stand by it.
When a docker is image is updated, you have to manually update it by typing docker pull cloudv/fault.
Please, once again try these commands specifically:
docker pull cloudv/fault:latest
docker run -tiv `pwd`:`pwd` -w `pwd` --rm cloudv/fault:latest fault -V
I have tested and found these commands to work just now on all of:
* Apple macOS

* Amazon Linux (our build server)

* Lubuntu 18.04.
I am getting the following error
docker: Error response from daemon: invalid volume specification: '/:/': invalid mount config for type "bind": invalid specification: destination can't be '/'.
See 'docker run --help'.

upon typing the commands, I am getting the following

zakir@zakir-virtual-machine:$ sudo docker run -tiv pwd:pwd -w pwd --rm cloudv/fault:latest fault -V
[sudo] password for zakir:
Fault 0.2.1. ©Cloud V 2019. All rights reserved.
zakir@zakir-virtual-machine:$ fault -V

Command 'fault' not found, did you mean:

command 'faust' from deb faust

Try: sudo apt install

Answer 20 · 2019-11-25T09:13:05.000Z

This is another problem

zakir@zakir-virtual-machine:~$ EXEC_PREFIX=</usr/local/bin> sudo ./iverilog_build.swift
bash: ./iverilog_build.swift: No such file or directory

Answer 21 · 2019-11-25T09:56:01.000Z

I am getting the following error
docker: Error response from daemon: invalid volume specification: '/:/': invalid mount config for type "bind": invalid specification: destination can't be '/'.
See 'docker run --help'.

upon typing the commands, I am getting the following

zakir@zakir-virtual-machine:~~$ sudo docker run -tiv pwd:pwd -w pwd --rm cloudv/fault:latest fault -V [sudo] password for zakir: Fault 0.2.1. ©Cloud V 2019. All rights reserved. zakir@zakir-virtual-machine:~~$ fault -V

Command 'fault' not found, did you mean:

command 'faust' from deb faust

Try: sudo apt install

It seems there is a misconception. Docker is not a universal installer. Docker is a containerized environment, again, akin to a virtual machine.

You can run Fault commands by invoking:

sudo docker run -tiv `pwd`:`pwd` -w `pwd` --rm cloudv/fault:latest <command here>

This is another problem

zakir@zakir-virtual-machine:~$ EXEC_PREFIX=</usr/local/bin> sudo ./iverilog_build.swift
bash: ./iverilog_build.swift: No such file or directory

This has nothing to do with this particular issue. This is the IcarusVerilog build script, which you should not be running if you're using a containerized environment. The containerized environment prepares everything for you.

Nevertheless:

A. You are not in the correct folder. Your home folder has no file called iverilog_build.swift. You need to navigate to the repository first.
B. </usr/local/bin> is not a valid path. By UNIX convention, angled brackets typically indicate that this is a configurable path with a default value of /usr/local/bin. You can elect to leave it blank and just run sudo ./iverilog_build.swift assuming you are satisfied with /usr/local/bin.