moby: oci runtime error: exec failed: fork/exec /proc/self/exe: no such file or directory

Output of docker version:

Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:42 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:42 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 9
 Running: 7
 Paused: 0
 Stopped: 2
Images: 146
Server Version: 1.11.1
Storage Driver: devicemapper
 Pool Name: docker-253:2-814311901-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 62.84 GB
 Data Space Total: 107.4 GB
 Data Space Available: 44.53 GB
 Metadata Space Used: 32.6 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.115 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /home/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
 Metadata loop file: /home/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 3.10.0-327.10.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 11.58 GiB
Name: docker1
ID: D7L5:RJ5K:CG6A:UCPB:CHOR:ND5B:GRXU:IE7L:CFMZ:ABYW:6PFK:LICR
Docker Root Dir: /home/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):

Steps to reproduce the issue:

#!/bin/bash -x
trap 'docker rmi oci_error ||:; docker rm -f oci_error ||:' EXIT
container_id=`docker run -d -v /tmp:/workspace --name oci_error centos:6 tail -f /dev/null`
docker exec --interactive=false $container_id date -u
image_id=`docker commit --pause=true $container_id oci_error`
docker exec --interactive=false $container_id date -u

Describe the results you received:

[root@docker1 ~]# ./oci_error.sh
+ trap 'docker rmi oci_error ||:; docker rm -f oci_error ||:' EXIT
++ docker run -d -v /tmp:/workspace --name oci_error centos:6 tail -f /dev/null
+ container_id=1a212e3fb4aa9a2d55260d404a639957d7126a8722a1b767ca8909ab839e590a
+ docker exec --interactive=false 1a212e3fb4aa9a2d55260d404a639957d7126a8722a1b767ca8909ab839e590a date -u
Sun May 15 10:41:11 UTC 2016
++ docker commit --pause=true 1a212e3fb4aa9a2d55260d404a639957d7126a8722a1b767ca8909ab839e590a oci_error
+ image_id=sha256:ae6002376259044f68f1b9e1826523aa7de5ee1499c5d8c7643e16f85be88a59
+ docker exec --interactive=false 1a212e3fb4aa9a2d55260d404a639957d7126a8722a1b767ca8909ab839e590a date -u
rpc error: code = 2 desc = "oci runtime error: exec failed: fork/exec /proc/self/exe: no such file or directory"+ docker rmi oci_error
Untagged: oci_error:latest
Deleted: sha256:ae6002376259044f68f1b9e1826523aa7de5ee1499c5d8c7643e16f85be88a59
Deleted: sha256:46674d91278a2c66c7bdd9c0dd7d7a860657f0f1eddb1f7c7e43b7a792ea434b
+ docker rm -f oci_error
oci_error

Describe the results you expected:

Commit should not brake container.

Additional information you deem important (e.g. issue happens only occasionally):

The issue is persistent.