circleci / docker Goto Github PK

Do you guys have a list of how CircleCI's docker differs from vanilla docker? We were having trouble with the test for jwilder/nginx-proxy due to a Btrfs error that seems to be specific to CircleCI's setup (see appropriate/nginx-proxy@5c6a635). It appears that running docker run --rm is not possible on CircleCI, but that docker rm -vf may be.

Looking at the docs at https://circleci.com/docs/docker, I don't see a good list of what can and cannot be done with Docker under CircleCI.

I tried to use docker 1.11.2(stable) version on CircleCI.
Use

machine:
  pre:
    - curl -sSL https://s3.amazonaws.com/circle-downloads/install-circleci-docker.sh | bash -s -- 1.11.2

  services:
    - docker
.
.

It install-circleci-docker.sh script seems old. will display 1.11.2 not available. CircleCI docker may not be properly installed.

Next, tried to

machine:
  pre:
    - curl -sSL https://github.com/circleci/docker/raw/docker-1.11.2/install-circleci-docker.sh | bash -s -- 1.11.2

  services:
    - docker
.
.

Passes the $1 version check, but https://s3-external-1.amazonaws.com/circle-downloads/docker-1.11.2-circleci is 403.

Why?
CircleCI has abandoned the provision of pre-building of the binary? or Do we not be able to use the stable version?

Trying to take advantage of the following:
https://docs.docker.com/engine/reference/builder/#/healthcheck

The following added to the dockerfile fails in circleci:

HEALTHCHECK CMD curl --fail http://localhost/ || exit 1

Even after logging in, the docker push command tries to get authentication details interactively. Passing the details as a heredoc fails with a docker error about invalid ioctl. I believe this may be related to a breaking change in the docker hub auth API in version 1.7. Where does Circle CI stand on installing an updated docker version? My attempts to script it in my circle.yml have failed miserably...

Hello Dear friends,

I am configuring CircleCI to automatically build and upload to Docker Hub multiple container of an open source library I contribute to.

Everything works fine except when I try to login on docker using the CLI.
I think that my builds have trouble to access private env vars, however I tried everything to fix it...

My configuration file is the following:

version: 2
jobs:
  build:
    working_directory: ~/build
    docker:
      - image: docker:git
    steps:
      - checkout
      - setup_remote_docker:
          reusable: true
          exclusive: true

      - run:
          name: Connect to Docker Hub
          command: |
            docker login -u ${DOCKER_USER} -p ${DOCKER_PASS}

I obtain the following error:

#!/bin/sh -eo pipefail
docker login -u $DOCKER_USER -p $DOCKER_PASS
"docker login" requires at most 1 argument.
See 'docker login --help'.

Usage:  docker login [OPTIONS] [SERVER] [flags]

Log in to a Docker registry
Exited with code 1

The variables are of course defined:

I would like to precise, that this runs on a branch of the main project and that I don't need to run it on project forks.

The project can be found here:

• CircleCI: https://circleci.com/gh/tensorlayer/tensorlayer/7
• Github: https://github.com/tensorlayer/tensorlayer/tree/Docker_Test

Thanks a lot for the help,

Jonathan

Currently only docker-compose 1.5.0 or older will work with the installed version of docker. This means version 2 of the docker-compose.yml format is incompatible with circle ci.

Not sure if this is the right place to ask, I've contacted the support on this recent, but it went silent. Please consider updating docker to something more recent. Circle right now runs 1.4.1, the most recent version is 1.6.2 which is light years ahead.

Hey,

Before upgrade mounting of the docker.sock was working it now fails and shutdown the container with a 255 exit code.

Does the location of the socket has changed ? Or this is the wanted behavior ? Anyway error output for that is not great (nothing is show) and user should be warned (i spent some hours figuring this out :( )