Machine executor still using Ubuntu 14.04 Trusty Tahr?

According to documentation it seems the machine executor is still using Ubuntu 14.04 Trusty Tahr. Trusty will be EOL in days. Is there any way to use a more recent machine executor?

Note that I’m using the machine executor so I can install snaps, which cannot happen within docker.


At the bottom of the docs I now see that I can use image: ubuntu-1604:201903-01. Unfortunately, it seems broken:

$ sudo apt update
Ign:1 stable InRelease
Get:2 stable Release [943 B]                                                                             
Get:3 stable Release.gpg [819 B]                                                                         
Hit:4 xenial InRelease                                                                                     
Hit:5 xenial InRelease                                                                                        
Hit:6 xenial InRelease                                                                            
Hit:7 xenial-security InRelease                              
Hit:8 xenial-updates InRelease                                     
Err:3 stable Release.gpg                                      
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E
Hit:9 xenial-backports InRelease                                   
Hit:10 xenial InRelease    
Hit:11 ./ InRelease
Hit:12 xenial InRelease
Ign:13 xenial InRelease
Err:14 xenial Release
  404  Not Found
Reading package lists... Done 
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E
E: The repository ' xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Hey Kyle,

Good point. We alway have an Ubuntu 16.04 image available with 18.04 in the pipeline for this year as well.

The default machine image may still be 14.04, but if it is it should be changed any day now. I’ll check in by Monday to help make sure that happens. That change should be happening today according to our previous announcement: Default machine executor image update

As far as the Ubuntu 16.04 image being broken, that I wasn’t aware of. I’ll check that and follow up here.

1 Like

Excellent, thanks @FelicianoTech. Thanks for the link to the announcement as well, I’ve now made sure I’m subscribed to that category so I see such things in the future.

1 Like

I’m seeing the same issue. Any update?

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.


Both the Ubuntu 16.04 and Ubuntu 14.04 machine images have had their repository issues fixed. apt-get update will work just fine now.

The default machine image has not yet changed over to Ubuntu 16.04 as originally planned. For anyone reading this in the future, here’s how you would use the newer Ubuntu image:

version: 2.1
      - build
      image: ubuntu-1604:201903-01
      - checkout
      - run:
          name: "Testing"
          command: echo "Hi"
1 Like