Trusty container update: 16.02.01

@FabianKoestring

Are you trying to use MongoDB? If so, it looks the service name has changed from mongodb to mongd on Trusty. We are now working on the fix. Sorry!

@shaneog

Yup, already working on that. The easiest fix would be adding the following to your circle.yml.

dependencies:
  pre:
    - type bundle &>/dev/null || gem install bundler

I just fixed bundler issue and rolled out the new image Trusty container update: 16.02.02

I get following error right now. @kimh we use php7.0.2.

((phpenv global "7.0.2")) returned exit code 1
rbenv: version `7.0.2' not installed Action failed: set php version to 7.0.2

@FabianKoestring How does your circle.yml look like?

It seems working for me: https://circleci.com/gh/kimh/trusty-test/60

1 Like
machine:
    php:
        version: 7.0.2
    timezone: Europe/Berlin

dependencies:
    pre:
        - sudo composer self-update
        - php -v
        - mysql -V
        - sed -i 's/^;//' ~/.phpenv/versions/$(phpenv global)/etc/conf.d/xdebug.ini
    override:
        - composer install --no-interaction
checkout:
    post:
        - git submodule sync
        - git submodule update --init

@FabianKoestring Although I can’t reproduce the exact error, I can see a thing that will not work on new Trusty image.

We install .phpenv and other (*vm and *env) under /opt/circleci, so can you change it to the following?

- sed -i 's/^;//' /opt/circleci/.phpenv/versions/$(phpenv global)/etc/conf.d/xdebug.ini

Ok. Running lsb_release -a returns

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.5 LTS
Release:        12.04
Codename:       precise

Expiremental setting Ubuntu 14.04 Trusty container is set to true.

That’s very strange. Maybe you haven’t trigger a new build by pushing to Github after changing to 14.04 (rebuilding will trigger a build with old setting) ?

2 Likes

Yea you was right. I had a pr open on github and triggerd it. Now i created a new one and everything works as expected.

@kimh thanks for helping me out.

I am having connecting to docker daemon on the Trusty containers. Is there a trick I am missing?

ubuntu@box69:~$ docker ps
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
ubuntu@box69:~$ docker daemon
FATA[0000] Error starting daemon: open /var/run/docker.pid: permission denied

Memcache appears to be installed on Trusty image, but is it started?

@tjchambers Sorry, I need to document this but we like to keep our default services as few as possible. This will give us many advantages such as more free memory for builds.

You can start memcached with the following circle.yml.

machines:
  services:
    - memcached

@jesh Sorry about that! This should be fixed now: Trusty container update: 16.02.03

Hi,

it looks like the new image is missing the PostGIS support.

ERROR: could not open extension control file “/usr/share/postgresql/9.4/extension/postgis.control”: No such file or directory
ERROR: could not open extension control file “/usr/share/postgresql/9.4/extension/postgis_topology.control”: No such file or directory
ERROR: could not open extension control file “/usr/share/postgresql/9.4/extension/postgis_tiger_geocoder.control”: No such file or directory

To replicate this, simply run the following commands in the postgres prompt:

CREATE EXTENSION postgis;
CREATE EXTENSION postgis_topology;
CREATE EXTENSION postgis_tiger_geocoder;
1 Like

@dlsniper Thanks for bringing this up. I’ll add PostGIS/GEOS support.

1 Like

@dlsniper I installed PostGIS extension in the container image.

ubuntu@box16:~$ psql -c 'CREATE EXTENSION postgis;'
CREATE EXTENSION
ubuntu@box16:~$ psql -c 'CREATE EXTENSION postgis_topology;'
CREATE EXTENSION
ubuntu@box16:~$ psql -c 'CREATE EXTENSION fuzzystrmatch;'
CREATE EXTENSION
ubuntu@box16:~$ psql -c 'CREATE EXTENSION postgis_tiger_geocoder;'
CREATE EXTENSION
1 Like

@kimh awesome! Thank you!

Looks like the heroku-cli is missing as well.