Getting an “operation not supported” error when trying to RUN something while building a docker image

I’m trying to build a docker image with the following command:

docker build -f conf/Dockerfile -t my_app_name .

The Dockerfile starts with:

  • What's the correct way to take automatic backups of docker volume containers?
  • Access services from docker swarm from public
  • “blkio.throttle.io_serviced” pseudo-files return zero values for one container
  • Docker registry on EC2
  • Docker - PG::ConnectionBad
  • Docker Base Image Size configured in daemon.json
  • FROM ubuntu:14.04
    COPY conf/pubkey pubkey
    RUN echo 'deb trusty universe' >> /etc/apt/sources.list \
      && apt-key add pubkey \
      && rm pubkey

    And it returns INFO[0000] operation not supported.

    Regardless of what I put after RUN (even RUN echo 1 fails)

    I tried running a shell in the intermediate docker image (docker run a7bb092… -it /bin/sh) but this just throws FATA[0000] Error response from daemon: Cannot start container a7bb092…: operation not supported

    How can I fix this?

  • Kitematic spins up new containers, but none of them showing up in Terminal
  • Docker - failed to connect to running image
  • Where can I configure the start user UID for Docker containers?
  • How to deploy multiple Services on Spring Boot? [closed]
  • How to add Zend Guard Loader support in docker php official image instance?
  • Android emulator in Docker
  • 2 Solutions collect form web for “Getting an “operation not supported” error when trying to RUN something while building a docker image”

    Well, turns out that if your machine had a kernel update but you didn’t restart yet then docker freaks out. Restarting the machine fixed that. Oops.

    This can happen if you do not have CONFIG_VETH selected in your kernel or don’t have lxc and cgroup.

    $ zcat /proc/config.gz | grep VETH

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.