Azure Ubuntu VM docker build apt-get 403 forbidden
0
I'm trying to configure Docker on an Azure VM (Ubuntu 18.04 LTS). The goal is to use Jenkins to deploy my applications to my Kubernetes cluster (following this tutorial).
But when I try to build a docker image inside this VM I got 403 errors during the "RUN apt-get update". While the VM itself can access those urls, it's only during the build of the docker image that I get 403 errors.
Sample of the output :
Err:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages
403 Forbidden [IP: 91.189.88.149 80]
Ign:34 http://archive.ubuntu.com/ubuntu xenial-backports/main all Packages
Ign:35 http://archive.ubuntu.com/ubuntu xenial-backports/restricted amd64 Packages
Ign:36 http://archive.ubuntu.com/ubuntu xenial-backports/restricted all Packages
Ign:37 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages
Ign:38 http://archive.ubuntu.com/ubuntu xenial-backports/universe all Packages
Ign:39 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 Packages
Ign:40 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse all Packages
Reading package lists...
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports Release' does not have a Release file.
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
I have found some similar questions like this one but none of the answers worked or explains exactly what happens in Azure (firewall or transparent proxy not used properly by the network of docker I guess).
Is there a specific configuration for docker, azure VM, ...?
Thank you.
azure docker 
azure-devops asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
add a comment |
0
I'm trying to configure Docker on an Azure VM (Ubuntu 18.04 LTS). The goal is to use Jenkins to deploy my applications to my Kubernetes cluster (following this tutorial).
But when I try to build a docker image inside this VM I got 403 errors during the "RUN apt-get update". While the VM itself can access those urls, it's only during the build of the docker image that I get 403 errors.
Sample of the output :
Err:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages
403 Forbidden [IP: 91.189.88.149 80]
Ign:34 http://archive.ubuntu.com/ubuntu xenial-backports/main all Packages
Ign:35 http://archive.ubuntu.com/ubuntu xenial-backports/restricted amd64 Packages
Ign:36 http://archive.ubuntu.com/ubuntu xenial-backports/restricted all Packages
Ign:37 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages
Ign:38 http://archive.ubuntu.com/ubuntu xenial-backports/universe all Packages
Ign:39 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 Packages
Ign:40 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse all Packages
Reading package lists...
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports Release' does not have a Release file.
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
I have found some similar questions like this one but none of the answers worked or explains exactly what happens in Azure (firewall or transparent proxy not used properly by the network of docker I guess).
Is there a specific configuration for docker, azure VM, ...?
Thank you.
azure docker azure-devops asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
The error shows the issue. It because the package resource cannot reach. You should change the source list.
– Charles Xu
Nov 15 '18 at 14:25
Ok which source list should I use?
– Alexandre Chenieux
Nov 15 '18 at 15:03
I tried mirrors for repositories and I also get 403 but I found a link between all 403 errors, it's always amd64 packages which are forbidden with the mirrors
– Alexandre Chenieux
Nov 15 '18 at 17:06
I mean the commandRUN apt-get updaterun in the Docker base image, so you should try to change the source list of the base image. Not your VM. Take a try.
– Charles Xu
Nov 16 '18 at 2:41
add a comment |
0
0
0
I'm trying to configure Docker on an Azure VM (Ubuntu 18.04 LTS). The goal is to use Jenkins to deploy my applications to my Kubernetes cluster (following this tutorial).
But when I try to build a docker image inside this VM I got 403 errors during the "RUN apt-get update". While the VM itself can access those urls, it's only during the build of the docker image that I get 403 errors.
Sample of the output :
Err:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages
403 Forbidden [IP: 91.189.88.149 80]
Ign:34 http://archive.ubuntu.com/ubuntu xenial-backports/main all Packages
Ign:35 http://archive.ubuntu.com/ubuntu xenial-backports/restricted amd64 Packages
Ign:36 http://archive.ubuntu.com/ubuntu xenial-backports/restricted all Packages
Ign:37 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages
Ign:38 http://archive.ubuntu.com/ubuntu xenial-backports/universe all Packages
Ign:39 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 Packages
Ign:40 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse all Packages
Reading package lists...
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports Release' does not have a Release file.
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
I have found some similar questions like this one but none of the answers worked or explains exactly what happens in Azure (firewall or transparent proxy not used properly by the network of docker I guess).
Is there a specific configuration for docker, azure VM, ...?
Thank you.
azure docker azure-devops asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
I'm trying to configure Docker on an Azure VM (Ubuntu 18.04 LTS). The goal is to use Jenkins to deploy my applications to my Kubernetes cluster (following this tutorial).
But when I try to build a docker image inside this VM I got 403 errors during the "RUN apt-get update". While the VM itself can access those urls, it's only during the build of the docker image that I get 403 errors.
Sample of the output :
Err:33 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages
403 Forbidden [IP: 91.189.88.149 80]
Ign:34 http://archive.ubuntu.com/ubuntu xenial-backports/main all Packages
Ign:35 http://archive.ubuntu.com/ubuntu xenial-backports/restricted amd64 Packages
Ign:36 http://archive.ubuntu.com/ubuntu xenial-backports/restricted all Packages
Ign:37 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages
Ign:38 http://archive.ubuntu.com/ubuntu xenial-backports/universe all Packages
Ign:39 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 Packages
Ign:40 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse all Packages
Reading package lists...
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports Release' does not have a Release file.
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.88.149 80]
I have found some similar questions like this one but none of the answers worked or explains exactly what happens in Azure (firewall or transparent proxy not used properly by the network of docker I guess).
Is there a specific configuration for docker, azure VM, ...?
Thank you.
azure docker azure-devops azure docker azure-devops asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
asked Nov 15 '18 at 14:20
Alexandre ChenieuxAlexandre Chenieux
84
84
The error shows the issue. It because the package resource cannot reach. You should change the source list.
– Charles Xu
Nov 15 '18 at 14:25
Ok which source list should I use?
– Alexandre Chenieux
Nov 15 '18 at 15:03
I tried mirrors for repositories and I also get 403 but I found a link between all 403 errors, it's always amd64 packages which are forbidden with the mirrors
– Alexandre Chenieux
Nov 15 '18 at 17:06
I mean the commandRUN apt-get updaterun in the Docker base image, so you should try to change the source list of the base image. Not your VM. Take a try.
– Charles Xu
Nov 16 '18 at 2:41
add a comment |
The error shows the issue. It because the package resource cannot reach. You should change the source list.
– Charles Xu
Nov 15 '18 at 14:25
Ok which source list should I use?
– Alexandre Chenieux
Nov 15 '18 at 15:03
I tried mirrors for repositories and I also get 403 but I found a link between all 403 errors, it's always amd64 packages which are forbidden with the mirrors
– Alexandre Chenieux
Nov 15 '18 at 17:06
I mean the commandRUN apt-get updaterun in the Docker base image, so you should try to change the source list of the base image. Not your VM. Take a try.
– Charles Xu
Nov 16 '18 at 2:41
The error shows the issue. It because the package resource cannot reach. You should change the source list.
– Charles Xu
Nov 15 '18 at 14:25
The error shows the issue. It because the package resource cannot reach. You should change the source list.
– Charles Xu
Nov 15 '18 at 14:25
Ok which source list should I use?
– Alexandre Chenieux
Nov 15 '18 at 15:03
Ok which source list should I use?
– Alexandre Chenieux
Nov 15 '18 at 15:03
I tried mirrors for repositories and I also get 403 but I found a link between all 403 errors, it's always amd64 packages which are forbidden with the mirrors
– Alexandre Chenieux
Nov 15 '18 at 17:06
I tried mirrors for repositories and I also get 403 but I found a link between all 403 errors, it's always amd64 packages which are forbidden with the mirrors
– Alexandre Chenieux
Nov 15 '18 at 17:06
I mean the command
RUN apt-get update run in the Docker base image, so you should try to change the source list of the base image. Not your VM. Take a try.– Charles Xu
Nov 16 '18 at 2:41
I mean the command
RUN apt-get update run in the Docker base image, so you should try to change the source list of the base image. Not your VM. Take a try.– Charles Xu
Nov 16 '18 at 2:41
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321479%2fazure-ubuntu-vm-docker-build-apt-get-403-forbidden%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321479%2fazure-ubuntu-vm-docker-build-apt-get-403-forbidden%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The error shows the issue. It because the package resource cannot reach. You should change the source list.
– Charles Xu
Nov 15 '18 at 14:25
Ok which source list should I use?
– Alexandre Chenieux
Nov 15 '18 at 15:03
I tried mirrors for repositories and I also get 403 but I found a link between all 403 errors, it's always amd64 packages which are forbidden with the mirrors
– Alexandre Chenieux
Nov 15 '18 at 17:06
I mean the command
RUN apt-get updaterun in the Docker base image, so you should try to change the source list of the base image. Not your VM. Take a try.– Charles Xu
Nov 16 '18 at 2:41