-
Notifications
You must be signed in to change notification settings - Fork 137
apt-get update' returned a non-zero code: 100 #19
Comments
That happens once in a while, also with other containers and is not under our control. I cannot suggest anything better than re-running I suggest we close this for lack of anything actionable. |
Maybe the |
Nope, and that has been discussed at considerable length -- see some of the the closed issue tickets (and we apologize for those being scattered over several related Rocker github repos). We often want current software and stable does not give that. And as an aside, repository server timeouts have nothing to do with the content you request from it ... |
@eddelbuettel FYI, this issue seems to arise fairly frequent...
|
@rvernica Thanks for blaming me personally ;-) Would appreciate a PR fixing it. |
@eddelbuettel ;-) should this be reopened then? I had a PR in #22. I'm not
sure what went wrong with it.
…On 17:37, Fri, Feb 10, 2017 Dirk Eddelbuettel ***@***.***> wrote:
@rvernica <https://github.com/rvernica> Thanks for blaming me personally
;-) Would appreciate a PR fixing it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOuIbnafYP0eFTbewvOxZxV895Es5Ksks5rbRDrgaJpZM4KqOL2>
.
|
@rvernica The problem was that it caused build failures. See my comment on that PR. |
@rvernica Let's just agree to disagree. |
I am facing the same issue for last few days, and even after trying multiple times, I am not able to build a container derived from rocker/shiny. It was working earlier. |
@shanFitGit I have a PR pending, #23, which should fix this. Since it is not yet merged, you can try basing your image off rvernica/shiny https://hub.docker.com/r/rvernica/shiny/ The image is build from this repository but with my patch applied. |
FWIW, I was able to work around this problem by adding |
I use, when this problem |
I had working containers derived from rocker/shiny before, but recently I always run into an error. The simplest Dockerfile to reproduce:
The text was updated successfully, but these errors were encountered: