Build Docker image

[davidclaeysquinones]

I saw this issue #5, and tried to build the project for myself.

I used the following command to build my image

docker build -t asksonic .

This is the Dockerfile I use :

FROM python:3.9-alpine

ENV SUBSONIC_PORT=443
ENV PORT=4545

ADD ./asksonic /app
ADD ./requirements.txt /app
ADD ./Procfile /app

RUN echo "ASKS_SUBSONIC_URL=$SUBSONIC_URL" > /app/.env
RUN echo "ASKS_SUBSONIC_USER=$SUBSONIC_USER" > /app/.env
RUN echo "ASKS_SUBSONIC_PASS=$SUBSONIC_PASS" > /app/.env
RUN echo "ASKS_SUBSONIC_PORT=$SUBSONIC_PORT" > /app/.env
RUN echo "ASKS_PORT=$PORT" > /app/.env

WORKDIR /app

RUN apk add -U --no-cache gcc libc-dev python3-dev openssl-dev musl-dev libffi-dev cargo pkgconfig git nodejs
#RUN apk add --update gcc libc-dev libffi-dev openssl-dev git nodejs npm
RUN pip3 install --upgrade pip
RUN pip3 install pyopenssl==17.5.0
RUN pip3 install cryptography==2.1.4
# RUN pip3 install -r ./asksonic/requirements.txt
RUN pip3 install git+https://github.com/srichter/flask-ask.git@flask2
RUN pip3 install gunicorn==20.1.0
RUN pip3 install py-sonic==0.7.9
RUN pip3 install requests==2.25.1
RUN npm install -g foreman

ENV PYTHONPATH=/usr/local/lib/python3.5/site-packages
ENV LC_ALL C.UTF-8
ENV LANG C.UTF-8

CMD ["nf", "start"]

This is the error log that I get as a result, at least the part that I managed to copy

    |     ^~~~~~
     /usr/include/openssl/dh.h:230:1: note: declared here
       230 | DECLARE_ASN1_ENCODE_FUNCTIONS_only_attr(OSSL_DEPRECATEDIN_3_0, DH, DHxparams)
           | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     build/temp.linux-x86_64-3.9/_openssl.c: In function 'Cryptography_HMAC_CTX_new':
     build/temp.linux-x86_64-3.9/_openssl.c:1457:5: warning: 'HMAC_CTX_new' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
      1457 |     return HMAC_CTX_new();
           |     ^~~~~~
     In file included from build/temp.linux-x86_64-3.9/_openssl.c:666:
     /usr/include/openssl/hmac.h:33:33: note: declared here
        33 | OSSL_DEPRECATEDIN_3_0 HMAC_CTX *HMAC_CTX_new(void);
           |                                 ^~~~~~~~~~~~
     build/temp.linux-x86_64-3.9/_openssl.c: In function 'Cryptography_HMAC_CTX_free':
     build/temp.linux-x86_64-3.9/_openssl.c:1469:5: warning: 'HMAC_CTX_free' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
      1469 |     return HMAC_CTX_free(ctx);
           |     ^~~~~~
     /usr/include/openssl/hmac.h:35:28: note: declared here
        35 | OSSL_DEPRECATEDIN_3_0 void HMAC_CTX_free(HMAC_CTX *ctx);
     error: command '/usr/bin/gcc' failed with exit code 1
     [end of output]

 note: This error originates from a subprocess, and is likely not a problem with pip.
 Rolling back uninstall of cryptography
 Moving to /usr/local/lib/python3.9/site-packages/cryptography-39.0.0.dist-info/
  from /usr/local/lib/python3.9/site-packages/~ryptography-39.0.0.dist-info
 Moving to /usr/local/lib/python3.9/site-packages/cryptography.libs/
  from /usr/local/lib/python3.9/site-packages/~ryptography.libs
 Moving to /usr/local/lib/python3.9/site-packages/cryptography/
  from /usr/local/lib/python3.9/site-packages/~ryptography
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> cryptography

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

The error log is actually so big that I'm not able to copy all of it. I suspect that it's a compiler error but have no clue why it's happening and what I could do to fix it. I've tried using libressl instead of openssl, using different python versions without much success.

I also strongly doubt that when it builds, the environment variables will work as intended. It's my first time building an image and I've not been able to test my image in a functional way yet.

Additionally when I build the image, Docker pulls an incredible amount of images and even makes some random containers, this might be happening because the build fails or because something else is wrong.

[srichter]

Does it also fail if you use the requements.txt instead of specifying packages manually?

[davidclaeysquinones]

For a while it seemed like your suggestion would work, but it didn't.

[srichter]

If it's the same package failing every time I'd reach out to them for help; not too sure why it's failing from the logs provided