tklx base debian Image possibly out of date

[maxmcd]

Switching to the latest tag fixed the issue for me, but in case it's helpful:

Running apt-get update followed by apt-get install -y --no-install-recommends git curl iputils-ping tcpdump returned the following error.

E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/libcurl4-openssl-dev_7.38.0-4+deb8u9_amd64.deb  404  Not Found [IP: 128.61.240.73 80]

E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/libcurl3_7.38.0-4+deb8u9_amd64.deb  404  Not Found [IP: 128.61.240.73 80]

E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/libcurl3-gnutls_7.38.0-4+deb8u9_amd64.deb  404  Not Found [IP: 128.61.240.73 80]

E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/curl_7.38.0-4+deb8u9_amd64.deb  404  Not Found [IP: 128.61.240.73 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ERROR: Service 'janus' failed to build: The command '/bin/sh -c apt-get install -y --no-install-recommends git     curl iputils-ping tcpdump' returned a non-zero code: 100

[krull]

Hi @maxmcd,

tklx doesn't have a 'latest' tag and hasn't been updated for quite some time now, collecting dust. (paging tklx crew -> @alonswartz, @JedMeister, @qrntz).

I have been playing with alternative base images, like bitnami/minideb, as they have CI involved in their build processes and you'll know you have the latest base to work on with.

my tklx builds for janus are in need of updates, but since they're in production, I need to thread lightly.

Stay tuned for an updated build.

[JedMeister]

Hi @krull & @maxmcd

Not sure about the apt errors. TKLX is currently still based on Jessie which should still work ok?! (Albeit quite out of date..).

tklx doesn't have a 'latest' tag and hasn't been updated for quite some time now, collecting dust.

Yes unfortunately, that is true in both counts. The former should be easy to solve, but probably not really worth the effort until we resolve the latter.

We're sad to say we don't see much of @qrntz these days :cry: and @alonswartz has been tied up with other stuff.

I've been busy maintaining our current monolithic builds and working hard to get a a new Stretch based version live. I've been pressuring Alon to make getting TKLX back on track something of a priority and he agrees in theory. If I knew more about docker style containers, then I'd be tempted to have a crack at it myself once we complete v15.0 release. But I think we're better off getting Alon to take care of it, unless of course we can engage someone else to take it on!? (Anyone who thinks they're up to the task email me jeremy@turnkeylinux.org)

Unfortunately, we're a small org with stretched labour resources. As you would no doubt be aware, saying yes to one thing, means saying no to 10 others! I really hope we can get TKLX back on track ASAP, but I hate to give empty promises, so I can't give any guaranteed timelines... Apologies that I don't have better or more exciting news...

[krull]

Hi @JedMeister

Thank you so much for dropping by to give us a heartbeat on your recent efforts, @JedMeister. Keep up the great work.

I for one am getting my mind wrapped around the CI processes that will make automated builds for docker-janus. This way I know that we will always have a baseline to work with on both dev and production environments.

Once I am done, I would love to take a look back at tklx-base, and see if we can have it be on parity with other docker image efforts.

[JedMeister]

Hey @krull

Once I am done, I would love to take a look back at tklx-base, and see if we can have it be on parity with other docker image efforts.

Awesome stuff! That'd be so cool if you can have a look at it.

Hopefully porting to Stretch shouldn't be too hard. If you have any joy, I'm pretty sure I have write access to the repo so should be able to merge any PRs you come up with.

Whilst I don't hold all the keys to the TKLX castle (e.g. access to Docker Hub), Alon does and I'm in a pretty good position to apply pressure if required! :wink:

PS please don't ever hesitate to ping me for updates on where things are up to. If I don't respond in a timely fashion, please feel free to bump me! :smile: