Closed LalatenduMohanty closed 9 years ago
Kubernetes version
[vagrant@localhost ~]$ sudo rpm -qa | grep kube
kubernetes-node-1.0.0-0.8.gitb2dafda.el7.x86_64
kubernetes-master-1.0.0-0.8.gitb2dafda.el7.x86_64
kubernetes-1.0.0-0.8.gitb2dafda.el7.x86_64
Docker version
[vagrant@localhost ~]$ sudo rpm -qa | grep docker
docker-selinux-1.7.1-108.el7.centos.x86_64
docker-python-1.4.0-108.el7.centos.x86_64
docker-registry-0.9.1-7.el7.x86_64
docker-1.7.1-108.el7.centos.x86_64
CentOS version
vagrant@localhost ~]$ cat /etc/centos-release
CentOS Linux release 7.1.1503 (Core)
[vagrant@localhost ~]$ uname -a
Linux localhost.localdomain 3.10.0-229.11.1.el7.x86_64 #1 SMP Thu Aug 6 01:06:18 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
How does this issue get assigned and prioritized?
@ggallen I could run this example now. Can you please do a retry?
@ggallen I think ur patch addressed the issue https://github.com/projectatomic/nulecule/commit/75760063c61024dda908fb0bf36b1e74057e77ec
This still fails for me:
[root@atomic helloapache]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.advancedhosters.com
* extras: mirror.solarvps.com
* updates: mirror.linux.duke.edu
No packages marked for update
[root@atomic helloapache]# git pull
Already up-to-date.
[root@atomic helloapache]# atomic run projectatomic/atomicapp
docker run -it --rm --privileged -v /root/nulecule/examples/helloapache:/atomicapp -v /run:/run -v /:/host --net=host --name atomicapp -e NAME=atomicapp -e IMAGE=projectatomic/atomicapp projectatomic/atomicapp -v run /atomicapp
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.
2015-08-25 11:21:27,149 - atomicapp.install - INFO - App name is projectatomic/atomicapp, will be populated to /atomicapp
2015-08-25 11:21:27,149 - atomicapp.utils - INFO - atomicapp.status.info.message=Loading app projectatomic/atomicapp .
2015-08-25 11:21:27,149 - atomicapp.nulecule_base - DEBUG - Path to answers file given, loading /atomicapp/answers.conf
2015-08-25 11:21:27,150 - atomicapp.utils - INFO - atomicapp.status.answer.message={"general": {"provider": "docker"}}
2015-08-25 11:21:27,150 - atomicapp.nulecule_base - DEBUG - {u'provider': u'docker'}
2015-08-25 11:21:27,245 - atomicapp.nulecule_base - DEBUG - Output of docker images cmd:
2015-08-25 11:21:27,245 - atomicapp.utils - INFO - atomicapp.status.info.message=Pulling image projectatomic/atomicapp ...
latest: Pulling from docker.io/projectatomic/atomicapp
f1b10cd84249: Already exists
c852f6d61e65: Already exists
7322fbe74aa5: Already exists
20d03cd76939: Already exists
5b5ab1f14e37: Already exists
36ee726aed08: Already exists
967d5b86a102: Already exists
b0ec2d6dbb23: Already exists
c2763353b20b: Already exists
c469bacf9245: Already exists
f7458ef927e7: Already exists
fb7e24b7480a: Already exists
2d6c35766db5: Already exists
d82b3d951679: Already exists
Digest: sha256:b8d07454f851195132c6f07d59a4bcc078238dcad97c5f9ed6ed79421f20db9b
Status: Image is up to date for docker.io/projectatomic/atomicapp:latest
2015-08-25 11:21:28,413 - atomicapp.nulecule_base - DEBUG - {u'provider': u'docker'}
2015-08-25 11:21:28,413 - atomicapp.install - DEBUG - Creating a container with name atomicapp-aRncNL
2015-08-25 11:21:28,413 - atomicapp.install - DEBUG - /usr/bin/docker run --name atomicapp-aRncNL --entrypoint /bin/true projectatomic/atomicapp
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.
2015-08-25 11:21:28,825 - atomicapp.utils - INFO - Using temporary directory /tmp/nulecule-bGZkEw
2015-08-25 11:21:28,825 - atomicapp.install - DEBUG - ['/usr/bin/docker', 'cp', 'atomicapp-aRncNL:/application-entity', '/tmp/nulecule-bGZkEw']
Error response from daemon: Could not find the file /application-entity in container atomicapp-aRncNL
2015-08-25 11:21:28,883 - atomicapp.utils - INFO - atomicapp.status.info.message=Copied app successfully.
atomicapp-aRncNL
2015-08-25 11:21:29,585 - atomicapp.utils - INFO - atomicapp.status.info.message=Loading app_id helloapache-app .
Traceback (most recent call last):
File "/usr/bin/atomicapp", line 9, in <module>
load_entry_point('atomicapp==0.1.9', 'console_scripts', 'atomicapp')()
File "/usr/lib/python2.7/site-packages/atomicapp-0.1.9-py2.7.egg/atomicapp/cli/main.py", line 227, in main
cli.run()
File "/usr/lib/python2.7/site-packages/atomicapp-0.1.9-py2.7.egg/atomicapp/cli/main.py", line 203, in run
args.func(args)
File "/usr/lib/python2.7/site-packages/atomicapp-0.1.9-py2.7.egg/atomicapp/cli/main.py", line 52, in cli_run
ae = Run(**vars(args))
File "/usr/lib/python2.7/site-packages/atomicapp-0.1.9-py2.7.egg/atomicapp/run.py", line 86, in __init__
install.install()
File "/usr/lib/python2.7/site-packages/atomicapp-0.1.9-py2.7.egg/atomicapp/install.py", line 138, in install
self.nulecule_base.loadMainfile(tmp_mainfile_path)
File "/usr/lib/python2.7/site-packages/atomicapp-0.1.9-py2.7.egg/atomicapp/nulecule_base.py", line 117, in loadMainfile
raise Exception("%s not found: %s" % (MAIN_FILE, path))
Exception: Nulecule not found: /tmp/nulecule-bGZkEw/application-entity/Nulecule
[root@atomic helloapache]#
That's a different problem, seems like https://github.com/projectatomic/atomicapp/issues/220
Sorry, I didn't notice the message had changed. I've seen this one numerous times. I'll look at projectatomic/atomicapp#220.
Closing this issue as it is resolved and for the new issue we have projectatomic/atomicapp#220
I tried to run the helloapache example from dockerhub on latest CentOS7 box, it failed to run. CC @ggallen
Here are the steps I followed
[1] https://hub.docker.com/r/projectatomic/helloapache/