Error when installing nextcloudpi container in docker

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP)
#1

Hi everyone

I’m super new here. Trying to install nextcloudpi container in docker running on my raspberry pi.
I believe I got docker running correctly. For the installation of the container I’m following this guide, but I got stuck on installing the container.

This is the line in the guide:

IP=192.168.1.130
docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf $IP

I wanted to provide a domain, so I created one on no-ip and changed the last part of the code to:

ownyourbits/nextcloudpi-armhf $mydomain.ddns.net

is that how to do it?

when running the command i get following message:

Status: Downloaded newer image for ownyourbits/nextcloudpi-armhf:latest
5931073779e9821610509bf3123400089f2950b45d3b1ccb183a35f8bee99f73
docker: Error response from daemon: driver failed programming external connectivity on endpoint nextcloudpi 
(3eb1b3238d824629b2a340f5903e229d9b43f3befc8b67e7e2e383d0493b8430):
Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.

where did I go wrong? What do I have to change?

Thank you in advance
Cheers

#2

you already have some web service listening on port 80, so docker cannot bind to that address because it is already in use

#3

@nachoparker
Ok. Thank you.
How do I know what is listening to port 80?
Or can I change the port nextcloud is using? If so, how?

#4

you can use other port in the -p switch or just forget about port 80

docker run -d -p 4443:4443 -p 443:443 -v ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf $IP

but you need port 80 atm for letsencript

#5

Thank you very much
I believe its PiHole thats not playing along. I just changed that.
But now when I try to run the docker run command again it tells me:

 You have to remove (or rename) that container to be able to reuse that name.

When I try to remove nextcloudpi it tells me there is no such file or directory

#6 
docker stop nextcloudpi
docker rm nextcloudpi
docker run ....
1 Like
#7

I think the installation worked but it’s not running. When i check

docker info

it shows:

Containers: 1
Running: 0
Paused: 0
Stopped: 1

also when using

docker start nextcloudpi

it doesnt start it

#8

it is stopped, you have to remove it

see which one it is

docker ps -a

delete it

docker rm nextcloudpi

and do the run command

#9

Sorry for asking again. I’d really like to have it running but it just wont work.
I deleted everything (docker and the container/image) to start a fresh install.
I installed docker according to this link and run also the command from there. I already changed the port of the pihole to 8080.

docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf $203.0.113.195  //The IP address would be the address of the computer i want to access the nextcloud from. Right?

after running this command i get:

Unable to find image 'ownyourbits/nextcloudpi-armhf:latest' locally
latest: Pulling from ownyourbits/nextcloudpi-armhf
17964a45024e: Pull complete
d3910f6b0ab1: Pull complete
ef9abc7c9c68: Pull complete
5fc74e852807: Pull complete
7bd03a9adad7: Pull complete
a5c5ea66bd0a: Pull complete
5e490f3f6730: Pull complete
35fe05c9eacd: Pull complete
6cfe05c4f211: Pull complete
0ed2575cb14b: Pull complete
15feeeb4f678: Pull complete
abfff1b6b6a8: Pull complete
Digest: sha256:07ff33904d8d144fc7e3caad2464316a000bb8b7dafb18ed53ada8454f44e495
Status: Downloaded newer image for ownyourbits/nextcloudpi-armhf:latest
1cdf45bb4fc0d8ef2c2cb8ba952c771f2655e06d92f07a1cd9cae5aa2e7ba3fe

according to the guide I should get a

init done

I never get that. Also when entering the command

docker logs -f nextcloudpi

I don’t get any answer.

I’m running on a Raspberry Pi Compute Module RPI-CM V1.1. Also running is PiHole and PiVPN

Thank you very much for your help and patience!

#10

You have an extra dollar sign. Also, it should be the IP address of the raspberry pi.

Just copy these three lines after stopping, removing the container as before and removing the volume with docker volume rm ncdata

IFACE=$( ip r | grep "default via" | awk '{ print $5 }' )
IP=$( ip a | grep "global $IFACE" | grep -oP '\d{1,3}(.\d{1,3}){3}' | head -1 )
docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi-armhf $IP
#11

I think something is jinxed. I can’t get it to work
Maybe I will just do a clean install of the nextcloudpi image.
Thank you very much for your help!

#12

Hi! I am trying to get Pi-Hole and NextCloudPi both working as docker containers managed with Portainer. I can get one or the other working but not both since they’re both fighting for port 80 and 443. Does anyone know the best way to do this?