Ubuntu 16.4 LTS cannot find openjdk-8-jdk
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I had to rebuild a docker container this past week, and as part of a 16.04 container creation, it does an apt-get install openjdk-8-jdk which fails with a 404 error.
Switching to apt-get install default-jdk tries to pull the same package and, likewise, fails with a 404 error. See below. As is normal practice, I run apt-get update before trying this.
Get:168 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxi6 amd64 2:1.7.6-1 [28.6 kB]
Get:169 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxrender1 amd64 1:0.9.9-0ubuntu1 [18.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Get:171 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ca-certificates-java all 20160321ubuntu1 [12.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Did the 16.04 repos get all wonky all of a sudden?
Thanks much!
16.04 apt jdk
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
asked Apr 9 at 16:00
Eric63
267
add a comment |Â
up vote
1
down vote
favorite
I had to rebuild a docker container this past week, and as part of a 16.04 container creation, it does an apt-get install openjdk-8-jdk which fails with a 404 error.
Switching to apt-get install default-jdk tries to pull the same package and, likewise, fails with a 404 error. See below. As is normal practice, I run apt-get update before trying this.
Get:168 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxi6 amd64 2:1.7.6-1 [28.6 kB]
Get:169 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxrender1 amd64 1:0.9.9-0ubuntu1 [18.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Get:171 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ca-certificates-java all 20160321ubuntu1 [12.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Did the 16.04 repos get all wonky all of a sudden?
Thanks much!
16.04 apt jdk
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
asked Apr 9 at 16:00
Eric63
267
Trysudo apt-get updatebefore installation again.
– N0rbert
Apr 9 at 16:01
I had the same problem on 17.10. I gave up trying to install JDK8 and just installed JDK9 which seems to be available on 16.04 repos as well.
– Jesus H
Apr 9 at 16:38
Yes, did the apt-get update as a matter of course, and noted in the above posting. The docker container is supposed to live long after the package is done and is being set-up per vendor recommendation.
– Eric63
Apr 9 at 16:51
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I had to rebuild a docker container this past week, and as part of a 16.04 container creation, it does an apt-get install openjdk-8-jdk which fails with a 404 error.
Switching to apt-get install default-jdk tries to pull the same package and, likewise, fails with a 404 error. See below. As is normal practice, I run apt-get update before trying this.
Get:168 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxi6 amd64 2:1.7.6-1 [28.6 kB]
Get:169 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxrender1 amd64 1:0.9.9-0ubuntu1 [18.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Get:171 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ca-certificates-java all 20160321ubuntu1 [12.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Did the 16.04 repos get all wonky all of a sudden?
Thanks much!
16.04 apt jdk
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
asked Apr 9 at 16:00
Eric63
267
I had to rebuild a docker container this past week, and as part of a 16.04 container creation, it does an apt-get install openjdk-8-jdk which fails with a 404 error.
Switching to apt-get install default-jdk tries to pull the same package and, likewise, fails with a 404 error. See below. As is normal practice, I run apt-get update before trying this.
Get:168 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxi6 amd64 2:1.7.6-1 [28.6 kB]
Get:169 http://archive.ubuntu.com/ubuntu xenial/main amd64 libxrender1 amd64 1:0.9.9-0ubuntu1 [18.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Get:171 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 ca-certificates-java all 20160321ubuntu1 [12.5 kB]
Err:170 http://security.ubuntu.com/ubuntu xenial-security/main amd64 openjdk-8-jre-headless amd64 8u151-b12-0ubuntu0.16.04.2
404 Not Found [IP: 91.189.88.162 80]
Did the 16.04 repos get all wonky all of a sudden?
Thanks much!
16.04 apt jdk
16.04 apt jdk
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
asked Apr 9 at 16:00
Eric63
267
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
asked Apr 9 at 16:00
Eric63
267
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
edited Apr 9 at 16:19
Byte Commander
59.4k26159267
59.4k26159267
asked Apr 9 at 16:00
Eric63
267
asked Apr 9 at 16:00
Eric63
267
asked Apr 9 at 16:00
Eric63
267
267
Trysudo apt-get updatebefore installation again.
– N0rbert
Apr 9 at 16:01
I had the same problem on 17.10. I gave up trying to install JDK8 and just installed JDK9 which seems to be available on 16.04 repos as well.
– Jesus H
Apr 9 at 16:38
Yes, did the apt-get update as a matter of course, and noted in the above posting. The docker container is supposed to live long after the package is done and is being set-up per vendor recommendation.
– Eric63
Apr 9 at 16:51
add a comment |Â
Trysudo apt-get updatebefore installation again.
– N0rbert
Apr 9 at 16:01
I had the same problem on 17.10. I gave up trying to install JDK8 and just installed JDK9 which seems to be available on 16.04 repos as well.
– Jesus H
Apr 9 at 16:38
Yes, did the apt-get update as a matter of course, and noted in the above posting. The docker container is supposed to live long after the package is done and is being set-up per vendor recommendation.
– Eric63
Apr 9 at 16:51
Try
sudo apt-get update before installation again.– N0rbert
Apr 9 at 16:01
Try
sudo apt-get update before installation again.– N0rbert
Apr 9 at 16:01
I had the same problem on 17.10. I gave up trying to install JDK8 and just installed JDK9 which seems to be available on 16.04 repos as well.
– Jesus H
Apr 9 at 16:38
I had the same problem on 17.10. I gave up trying to install JDK8 and just installed JDK9 which seems to be available on 16.04 repos as well.
– Jesus H
Apr 9 at 16:38
Yes, did the apt-get update as a matter of course, and noted in the above posting. The docker container is supposed to live long after the package is done and is being set-up per vendor recommendation.
– Eric63
Apr 9 at 16:51
Yes, did the apt-get update as a matter of course, and noted in the above posting. The docker container is supposed to live long after the package is done and is being set-up per vendor recommendation.
– Eric63
Apr 9 at 16:51
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
Did you do sudo apt-get update recently? If not, do that, then try again.
The 404 error is that it's hunting a specific version of the package that is not available on the repos anymore, and this usually happens when your repository 'state' information is out of date. Usually a call to sudo apt-get update will fix that problem, and then you can retry the sudo apt-get install command you were trying to run again.
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
add a comment |Â
up vote
0
down vote
Thomas, the repos have been fixed. Rerunning sudo apt-get update now -- I mean, after Thursday, 4/12/2018, resolves the issue.
Thanks much!
answered Apr 13 at 13:08
Eric63
267
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Did you do sudo apt-get update recently? If not, do that, then try again.
The 404 error is that it's hunting a specific version of the package that is not available on the repos anymore, and this usually happens when your repository 'state' information is out of date. Usually a call to sudo apt-get update will fix that problem, and then you can retry the sudo apt-get install command you were trying to run again.
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
add a comment |Â
up vote
2
down vote
Did you do sudo apt-get update recently? If not, do that, then try again.
The 404 error is that it's hunting a specific version of the package that is not available on the repos anymore, and this usually happens when your repository 'state' information is out of date. Usually a call to sudo apt-get update will fix that problem, and then you can retry the sudo apt-get install command you were trying to run again.
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Did you do sudo apt-get update recently? If not, do that, then try again.
The 404 error is that it's hunting a specific version of the package that is not available on the repos anymore, and this usually happens when your repository 'state' information is out of date. Usually a call to sudo apt-get update will fix that problem, and then you can retry the sudo apt-get install command you were trying to run again.
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
Did you do sudo apt-get update recently? If not, do that, then try again.
The 404 error is that it's hunting a specific version of the package that is not available on the repos anymore, and this usually happens when your repository 'state' information is out of date. Usually a call to sudo apt-get update will fix that problem, and then you can retry the sudo apt-get install command you were trying to run again.
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
answered Apr 9 at 16:02
Thomas Ward♦
41.4k23112166
41.4k23112166
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
add a comment |Â
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
Did that as a matter of course. Note that trying to install metapackage "default-jdk" ends up with the same result.
– Eric63
Apr 9 at 16:49
add a comment |Â
up vote
0
down vote
Thomas, the repos have been fixed. Rerunning sudo apt-get update now -- I mean, after Thursday, 4/12/2018, resolves the issue.
Thanks much!
answered Apr 13 at 13:08
Eric63
267
add a comment |Â
up vote
0
down vote
Thomas, the repos have been fixed. Rerunning sudo apt-get update now -- I mean, after Thursday, 4/12/2018, resolves the issue.
Thanks much!
answered Apr 13 at 13:08
Eric63
267
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Thomas, the repos have been fixed. Rerunning sudo apt-get update now -- I mean, after Thursday, 4/12/2018, resolves the issue.
Thanks much!
answered Apr 13 at 13:08
Eric63
267
Thomas, the repos have been fixed. Rerunning sudo apt-get update now -- I mean, after Thursday, 4/12/2018, resolves the issue.
Thanks much!
answered Apr 13 at 13:08
Eric63
267
answered Apr 13 at 13:08
Eric63
267
answered Apr 13 at 13:08
Eric63
267
answered Apr 13 at 13:08
Eric63
267
267
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1023384%2fubuntu-16-4-lts-cannot-find-openjdk-8-jdk%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Try
sudo apt-get updatebefore installation again.– N0rbert
Apr 9 at 16:01
I had the same problem on 17.10. I gave up trying to install JDK8 and just installed JDK9 which seems to be available on 16.04 repos as well.
– Jesus H
Apr 9 at 16:38
Yes, did the apt-get update as a matter of course, and noted in the above posting. The docker container is supposed to live long after the package is done and is being set-up per vendor recommendation.
– Eric63
Apr 9 at 16:51