Error on docker-compose up

PostPollux commented 5 years ago

Unfortunately I always get an error at build step 7 when I fire up the docker-compose up command. Any Idea how to fix that?

I'm running this under linux Manjaro with docker 18.06.1-ce

Here is the log:

[johannes-pc docker-taiga]# docker-compose up
Building taiga
Step 1/46 : FROM python:3.5
 ---> 1419e5e87f7c
Step 2/46 : MAINTAINER Benjamin Hutchins <ben@hutchins.co>
 ---> Using cache
 ---> 584cd9e8b503
Step 3/46 : ENV DEBIAN_FRONTEND noninteractive
 ---> Using cache
 ---> ccdd6932248d
Step 4/46 : ENV NGINX_VERSION 1.9.7-1~jessie
 ---> Using cache
 ---> df4d7b2a7c7e
Step 5/46 : RUN apt-key adv   --keyserver hkp://pgp.mit.edu:80   --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62
 ---> Using cache
 ---> d5a44b51e4b8
Step 6/46 : RUN echo "deb http://nginx.org/packages/mainline/debian/ jessie nginx" >> /etc/apt/sources.list
 ---> Using cache
 ---> 1ffe2e0b7c23
Step 7/46 : RUN set -x;     apt-get update     && apt-get install -y --no-install-recommends         locales         gettext         ca-certificates         nginx=${NGINX_VERSION}     && rm -rf /var/lib/apt/lists/*
 ---> Running in 5a860d78966e
+ apt-get update
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://deb.debian.org/debian stretch Release.gpg [2434 B]
Get:6 http://nginx.org/packages/mainline/debian jessie InRelease [2865 B]
Get:7 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [454 kB]
Get:8 http://deb.debian.org/debian stretch-updates/main amd64 Packages [5152 B]
Get:9 http://deb.debian.org/debian stretch/main amd64 Packages [7099 kB]
Get:10 http://nginx.org/packages/mainline/debian jessie/nginx amd64 Packages [52.9 kB]
Fetched 7919 kB in 5s (1511 kB/s)
Reading package lists...
+ apt-get install -y --no-install-recommends locales gettext ca-certificates nginx=1.9.7-1~jessie
Reading package lists...
Building dependency tree...
Reading state information...
ca-certificates is already the newest version (20161130+nmu1+deb9u1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nginx : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable
E: Unable to correct problems, you have held broken packages.
ERROR: Service 'taiga' failed to build: The command '/bin/sh -c set -x;     apt-get update     && apt-get install -y --no-install-recommends         locales         gettext         ca-certificates         nginx=${NGINX_VERSION}     && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

jialvarez commented 5 years ago

I've solved that by modifying Dockerfile. Instead this:

RUN set -x; \ apt-get update \ && apt-get install -y --no-install-recommends \ locales \ gettext \ ca-certificates \ nginx=${NGINX_VERSION} \ && rm -rf /var/lib/apt/lists/*

I've added these two lines to download and install libssl1.0.0:

RUN set -x; \ apt-get update \ && wget "http://ftp.se.debian.org/debian/pool/main/o/openssl/libssl1.0.0_1.0.2l-1~bpo8+1_amd64.deb" \ && dpkg -i libssl1.0.0_1.0.2l-1~bpo8+1_amd64.deb \ && apt-get install -y --no-install-recommends \ locales \ gettext \ ca-certificates \ nginx=${NGINX_VERSION} \ && rm -rf /var/lib/apt/lists/*

panosru commented 5 years ago

I also have an issue with docker-compose up

Could anyone give me any suggestion? :/

Thanks!

UPDATE

That solved the issue:

RUN apt-key adv \
  --no-tty \
  --keyserver hkp://ha.pool.sks-keyservers.net \
  --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62

I also had to turn off my MacOS Firewall

In addition to what @jialvarez suggested

panosru commented 5 years ago

I now receive a new error at step 37/46

jialvarez commented 5 years ago

You have to add this line: ENV TAIGA_SSL_BY_REVERSE_PROXY False

below of line saying: ENV TAIGA_SSL False

panosru commented 5 years ago

@jialvarez thanks for the tip! I forgot to update my latest comment as I already done that ref: #52

Now I have another issue lol

http://localhost/ is just not working for some reason

UPDATE

From what I can understand I have to place a sleep so taiga will wait for the database to initialise?

UPDATE

I applied the changes suggested in #66 and now I'm waiting for the miracle to happen :lol:

panosru commented 5 years ago

Seems that I'm not the only one stuck on that point, @jialvarez from what I saw in #67 you also stuck there, how did you solve this? Similar issues: #24 and #30

UPDATE

based on https://github.com/taigaio/taiga-back/issues/958 and https://github.com/taigaio/taiga-back/issues/958 it seems that it is safe to remove python manage.py loaddata initial_role from docker-entrypoint.sh since most likely it was a command that was required for an older version of taiga (not yet confirmed, I'm still testing it).

UPDATE

nope, nothing happened, still stuck on the same messages, I guess I'll give up on taiga until they officially support docker or there will be a working docker repository that won't be a pain in the ass to get it up and running.

UPDATE

I overcome the message, setup now gone fine but when I try to run http://localhost/ I'm getting:

on terminal:

jialvarez commented 5 years ago

Hi, in my case, when installation seemed to be stuck in that point, I've just tried to access to the Taiga URL and everything was running OK.

I didn't do nothing far away from adding the line ENV TAIGA_SSL_BY_REVERSE_PROXY False and solved the step 7:

The following packages have unmet dependencies: nginx : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable E: Unable to correct problems, you have held broken packages.

to fix libssl1.0.0 installation.

thomasrossetto commented 5 years ago

Seems that I'm not the only one stuck on that point, @jialvarez from what I saw in #67 you also stuck there, how did you solve this? Similar issues: #24 and #30

UPDATE

based on taigaio/taiga-back#958 and taigaio/taiga-back#958 it seems that it is safe to remove python manage.py loaddata initial_role from docker-entrypoint.sh since most likely it was a command that was required for an older version of taiga (not yet confirmed, I'm still testing it).

UPDATE

nope, nothing happened, still stuck on the same messages, I guess I'll give up on taiga until they officially support docker or there will be a working docker repository that won't be a pain in the ass to get it up and running.

UPDATE

I overcome the message, setup now gone fine but when I try to run http://localhost/ I'm getting:

on terminal:

Hi, try to restart taiga service :) docker-compose restart taiga

gerroon commented 5 years ago

I have an issue with it too, i think it is the same

Step 5/47 : RUN apt-key adv   --keyserver hkp://pgp.mit.edu:80   --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62                                                                        
 ---> Running in b17c8f82f0aa
Warning: apt-key output should not be parsed (stdout is not a terminal)
Executing: /tmp/apt-key-gpghome.bcMv9072po/gpg.1.sh --keyserver hkp://pgp.mit.edu:80 --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62                                                    
gpg: keyserver receive failed: No data
ERROR: Service 'taiga' failed to build: The command '/bin/sh -c apt-key adv   --keyserver hkp://pgp.mit.edu:80   --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62' returned a non-zero code: 2

changing the gpg server did not help at all

Step 5/47 : RUN apt-key adv   --no-tty   --keyserver hkp://ha.pool.sks-keyservers.net   --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62
 ---> Running in e581c264e3e2
Warning: apt-key output should not be parsed (stdout is not a terminal)
Executing: /tmp/apt-key-gpghome.PJ9mPkxUHu/gpg.1.sh --no-tty --keyserver hkp://ha.pool.sks-keyservers.net --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62
gpg: keyserver receive failed: Cannot assign requested address
ERROR: Service 'taiga' failed to build: The command '/bin/sh -c apt-key adv   --no-tty   --keyserver hkp://ha.pool.sks-keyservers.net   --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62' returned a non-zero code: 2

jialvarez commented 5 years ago

@gerroon this one worked for me in step 5:

RUN apt-key adv \ --keyserver keyserver.ubuntu.com \\ --recv-keys 379CE192D401AB61

gerroon commented 5 years ago

@jialvarez

Thanks it works. I do know what is up with these key servers failing like that

sabatmonk commented 5 years ago

@panosru If you are running docker for windows, postgres is not able to start, you need to create a volume with docker volume create postgres_database then use it in the compose file like this - postgres_database:/var/lib/postgresql/data and adding that at the end volumes: postgres_database: external: true

This is really ugly, and a bad workaround, but the issue with postgress has been closed without solution for a couple of years now... https://github.com/docker/for-win/issues/445

linkerx commented 3 years ago

the solution to the problem:

nginx : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable E: Unable to correct problems, you have held broken packages.

is to force an earlier version of python image

change:

FROM python:3.5

to:

FROM python:3.5.2

benhutchins / docker-taiga