MartinSahlen/cloud-functions-python

Ubuntu 17.04 reached EOL

opyate opened this issue · 4 comments

When building the 3.5 image, it fails with:

Reading package lists...
W: The repository 'http://security.ubuntu.com/ubuntu zesty-security Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu zesty Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu zesty-updates Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu zesty-backports Release' does not have a Release file.
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/zesty-security/universe/source/Sources  404  Not Found [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/zesty/universe/source/Sources  404  Not Found [IP: 91.189.88.152 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/zesty-updates/universe/source/Sources  404  Not Found [IP: 91.189.88.152 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/zesty-backports/universe/binary-amd64/Packages  404  Not Found [IP: 91.189.88.152 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

This is because 17.04 reached end-of-life a few weeks ago.

Merely using the 17.10 image has a new error:

Step 1/4 : FROM ubuntu:17.10
 ---> a8ad041f5225
Step 2/4 : RUN   apt-get update &&   DEBIAN_FRONTEND=noninteractive     apt-get install -y       python3.5       python3-pip   &&   apt-get clean &&   rm -rf /var/lib/apt/lists/*
 ---> Using cache
 ---> e205e19f7ef7
Step 3/4 : RUN python3.5 -m pip install pip==9.0.1
 ---> Running in 06f16e1152a7
/bin/sh: 1: python3.5: not found

I'll try and solve it, but if anyone has any ideas...

@MartinSahlen I suppose you can push your known working pre-built images to Docker hub for our benefit? That way pycloudfn doesn't need to build an image each and every time for each and every user?

Related to #21

I've added "bring your own image" in #30 but also an alternative 3.5 Dockerfile which works.

Hi @opyate, just wondering if you were able to merge #30 or if there's any other workaround to make it work in the meantime? Thank you.