Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to Load&Run Docker Container #18

Closed
louislxw opened this issue Dec 23, 2019 · 9 comments
Closed

Failed to Load&Run Docker Container #18

louislxw opened this issue Dec 23, 2019 · 9 comments

Comments

@louislxw
Copy link

Hi,

I am trying to install and run the vitis-ai-docker-tools following the instructions under "Getting Started". I was able to install docker and put my linux user in the group docker. However, there is an issue when I ran the command "./docker_run.sh xilinx/vitis-ai:tools-1.0.0-cpu". Error messages:

docker: unknown server OS: .
See 'docker run --help'.

Could anyone support with this issue? Thanks!

Regards,
Louis

@louislxw louislxw closed this as completed Jan 6, 2020
@AlbertaBeef
Copy link

Louis,
I am running into the same issue, did you find a fix ? can you share ?
Mario.

@louislxw
Copy link
Author

Louis,
I am running into the same issue, did you find a fix ? can you share ?
Mario.

Hi Mario,

I followed the instructions carefully twice and solved the previous issue.
I guess you were able to install docker with no issue. Be careful with the 2nd step "Ensure your linux user is in the group docker" (https://docs.docker.com/install/linux/linux-postinstall/). Specifically, verify that you can run the following command without sudo
$ docker run hello-world

Regards,
Louis

@AlbertaBeef
Copy link

Thank you Louis, that fixed the issue.

hanxue pushed a commit that referenced this issue Jul 8, 2020
bug fixes; removed unnecessary files
@rmsys
Copy link

rmsys commented Nov 12, 2020

I know this post is old but maybe help somebody.

if you try:

ubuntu@ip:/$ docker run hello-world
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/cont.

so, update permission:
ubuntu@ip:/$ sudo chmod 666 /var/run/docker.sock

@hanxue
Copy link
Contributor

hanxue commented Nov 12, 2020

@rmsys good workaround. Changing the permissions of /var/run/docker.sock by hand will only fix the problem temporarily. The permissions of /var/run/docker.sock will be reset when the Docker daemon is next reset.

A more permanent solution is to create the docker group on your host machine and add the users running docker to the docker group per https://docs.docker.com/install/linux/linux-postinstall/

@mo979
Copy link

mo979 commented May 5, 2021

I met the problem and added sudo before the shell command. Then it ran successfully.

@tan24012
Copy link

aa
Makefile.zip

@GrabbenD
Copy link

I solved this by:

$ sudo usermod -G docker -a $USER
$ sudo service docker start # Or to persist: $ sudo systemctl enable docker --now

@gregpalaci
Copy link

gregpalaci commented Sep 30, 2023

docker/for-mac#6531 (comment)

I was running into this on v4.14.x, v4.15.0, and v14.16.2 -- ended up identifying the following fix:

Check your ~/.docker/config.json file for a currentContext key. e.g. "currentContext": "desktop-linux"

In my case, removing currentContext from config.json did the trick!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants