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

Error by starting docker in a Virtual Machine #29

Closed
dolphikcode opened this issue Oct 30, 2019 · 7 comments
Closed

Error by starting docker in a Virtual Machine #29

dolphikcode opened this issue Oct 30, 2019 · 7 comments

Comments

@dolphikcode
Copy link

dolphikcode commented Oct 30, 2019

I have installed IOTstack on Virtual Machine to check how it works (used instruction from github) and when trying to start docker I get:
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

I have restarted and recreated yaml but without any better result... Is IOTstack possible to run only on RPi?

@gcgarner
Copy link
Owner

gcgarner commented Oct 30, 2019

The project should run on most Debain based systems. All the images support multi architecture .

I did a quick online search for people having similar issues, there appears to be certain cases that you can't run docker inside a VM. Such as having docker on your local machine and then running a VM with docker. The other option is to check that your virtualisation settings are enabled in your BIOS.

If you have success please let me know about your solution and i will pin the issue

@dolphikcode
Copy link
Author

dolphikcode commented Oct 30, 2019

No docker on host and without virtualisation in BIOS it would not be possible to run VM :)

I have found something like this working (running from ~/IOTstack):
export DOCKER_HOST=127.0.0.1:2375
sudo service docker start
sudo docker-compose up -d

@gcgarner gcgarner changed the title Error by starting docker Error by starting docker in a Virtual Machine Oct 30, 2019
@gcgarner
Copy link
Owner

No docker on host and without virtualisation in BIOS it would not be possible to run VM :)

fair point

Just to confirm did that solve your issue. And if so does it persist over a reboot? I would like to Pin the solution for others if it does.

Also which distro where you using?

@dolphikcode
Copy link
Author

I'm using xUbuntu to have VM lightweight, but normal Ubuntu should also work.

After restarting just need to be started by:
sudo service docker start
sudo docker-compose up -d

@gcgarner
Copy link
Owner

Thanks to @dolphikcode for this solution:

if you get the following error:

ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
Run:

No docker on host and without virtualisation in BIOS it would not be possible to run VM :)

run:

export DOCKER_HOST=127.0.0.1:2375
sudo service docker start
sudo docker-compose up -d

after rebooting you will still need to run

sudo service docker start
sudo docker-compose up -d

@gcgarner gcgarner pinned this issue Oct 30, 2019
@Paulf007
Copy link
Contributor

Paulf007 commented Oct 30, 2019

I gave it a Quick go as this will make testing a lot easier I get the following error:

pi@IOT-Test:~/IOTstack$ sudo docker-compose up -d Pulling portainer (portainer/portainer:)... latest: Pulling from portainer/portainer ERROR: no matching manifest for unknown in the manifest list entries
Apologies : Using VM VirtualBox with Debian 10 (32 bit)

@gcgarner
Copy link
Owner

gcgarner commented Oct 30, 2019

I had a look at portainer's manifest info and it looks like it is only build for amd64 ARM and PPC

@Paulf007 a 32bit OS is the issue, there is no x86_64 portainer image for you to pull. I've added this issue to the README

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

3 participants