a prepackaged development environment filled with production-grade pre-configured tools that makes container development easier
License: GNU General Public License v2.0
Monday May 11, 2015 at 12:30 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#10
Signed-off-by: Lalatendu Mohanty [email protected]
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/10/commits
Read #68 (comment)
Scratch build: https://cbs.centos.org/koji/taskinfo?taskID=18983
CC @navidshaikh
sudo systemctl status docker
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
Drop-In: /usr/lib/systemd/system/docker.service.d
└─flannel.conf
Active: failed (Result: exit-code) since Wed 2015-08-19 11:31:22 EDT; 5min ago
Docs: http://docs.docker.com
Process: 814 ExecStart=/usr/bin/docker -d $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=1/FAILURE)
Main PID: 814 (code=exited, status=1/FAILURE)
CGroup: /system.slice/docker.service
Aug 19 11:31:22 localhost.localdomain docker[814]: time="2015-08-19T11:31:22.503471246-04:00" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)"
Aug 19 11:31:22 localhost.localdomain docker[814]: time="2015-08-19T11:31:22.544865763-04:00" level=fatal msg="Error starting daemon: error initializing graphdriver: Unknown option dm.fs"
Aug 19 11:31:22 localhost.localdomain systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Aug 19 11:31:22 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.
Aug 19 11:31:22 localhost.localdomain systemd[1]: Unit docker.service entered failed state.
This isn't an urgent question, but rather a more general question regarding documentation scope (once we have a clear documentation story...). One of the challenges with open source programming can be in finding recommendations for good tools to pair up with your chosen programming language. Folks that opt for an all-inclusive IDE can get a reasonable selection, but there often isn't a good starting place for finding independent analysis programs, or looking into platform specific tools like strace et al for *nix, or sysinternals for Windows.
For Python, for example, there's http://www.vrplumber.com/programming/runsnakerun/ for visualising profiler results and memory usage (wxPython based) and https://jiffyclub.github.io/snakeviz/ for a different view of profiler results (browser based), as well as pylint for structural code checking, and mypy for more advanced static analysis (based on type inference).
For Fedora/RHEL/CentOS generally, there are the components that go into making up the RHEL Developer Toolset (https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/3-Beta/html-single/User_Guide/index.html#tabl-Red_Hat_Developer_Toolset-About), while for JBoss (and the JVM in general) there are those that go into JBoss Developer Studio (https://www.jboss.org/products/devstudio/overview/).
For JavaScript and PHP, projects like Facebook's Nuclide IDE provide a good way for new developers to gain from the experience of Facebook's web and mobile development teams.
Thursday Jun 18, 2015 at 13:40 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#39
Github : https://github.com/bkabrda/atomicapp-builder CC @bkabrda @kbsingh
A question that occasionally comes up with the current ADB name is the possible confusion with the Android Developer Bundle.
I thought of BCL in terms of "the upstream for the RHEL CDK", and then realised there was a nice backronym for that: Build Containers Locally
(It should really be BCJ, but I can't think of a neat backronym for that)
Monday May 11, 2015 at 16:14 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#12
As per Langdon's suggestion we need to add libyaml-devel to the ks file. As atomicapp has a dependency on it.
Friday May 08, 2015 at 13:12 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#6
Signed-off-by: Lalatendu Mohanty [email protected]
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/6/commits
We should be able to create an OpenShift instance so that it can be used by Atomic Apps to run.
For example wordpress-centos7-atomicapp [1] should be able to run on OpenShift environment provided by adb.
[1] https://github.com/projectatomic/nulecule/tree/master/examples/wordpress-centos7-atomicapp
Monday May 11, 2015 at 15:55 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#11
As I dont want to docker pull them each time I vagrant destroy'ed a box
Friday May 08, 2015 at 12:34 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#5
Hi, could you please put a minimum docker version (>=1.6) in the kickstart file, best case would be to adopt RHEL docker 1.6
The atomic tool should be >0.0.9 too
Wednesday May 13, 2015 at 16:32 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#28
Thursday Jul 30, 2015 at 11:49 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#53
In newer builds of atomicapp vagrant box we are seeing below issue. This issue will be used to see if the issue is with the Vagrant box.
vagrant@localhost ~]$ docker --version
Docker version 1.6.2, build ba1f6c3/1.6.2
vagrant@localhost ~]$ sudo docker pull centos/httpd
latest: Pulling from docker.io/centos/httpd
6941bfcbbfca: Pull complete
6941bfcbbfca: Download complete
41459f052977: Download complete
fd44297e2ddb: Error downloading dependent layers
06d0d6cc01fc: Download complete
1634f53d8d34: Download complete
f5d7d1d76e27: Download complete
72d3df4bba94: Download complete
4617321b355e: Download complete
9f74023d48fc: Download complete
d3d3700d1c33: Download complete
dabbf6687da0: Download complete
9c9ec0c21871: Download complete
9c9ec0c21871: Error pulling image (latest) from docker.io/centos/httpd, Driver devicemapper failed to create image rootfs fd44297e2ddb050ec4fa9752b7a4e3a8439061991886e2091e7c1f007c906d75: Error running DeviceCreFATA[0109] Error pulling image (latest) from docker.io/centos/httpd, Driver devicemapper failed to create image rootfs fd44297e2ddb050ec4fa9752b7a4e3a8439061991886e2091e7c1f007c906d75: Error running DeviceCreate (createSnapDevice) dm_task_run failed 
Monday May 11, 2015 at 16:20 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#13
Could you please add nfs-utils to the ks so that it is there from the get go (rather than having to install it on v-up)
With latest atomicapp/dev box, I am unable to create the pods
[vagrant@localhost ~]$ rpm -q docker kubernetes
docker-1.7.1-108.el7.centos.x86_64
kubernetes-1.0.0-0.8.gitb2dafda.el7.x86_64
[vagrant@localhost ~]$ kubectl get nodes
NAME LABELS STATUS
127.0.0.1 kubernetes.io/hostname=127.0.0.1 Ready
[vagrant@localhost ~]$ kubectl get rc
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
[vagrant@localhost ~]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
[vagrant@localhost ~]$ kubectl run nginx --image=nginx
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
nginx nginx nginx run=nginx 1
[vagrant@localhost ~]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
[vagrant@localhost ~]$ # waited for few mins, no activity
[vagrant@localhost ~]$ kubectl get pods
NAME READY STATUS RESTARTS AGE
[vagrant@localhost ~]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[vagrant@localhost ~]$ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
[vagrant@localhost ~]$ systemctl status kube-apiserver
kube-apiserver.service - Kubernetes API Server
Loaded: loaded (/etc/systemd/system/kube-apiserver.service; enabled)
Active: active (running) since Fri 2015-08-21 05:05:34 EDT; 39min ago
Docs: https://github.com/GoogleCloudPlatform/kubernetes
Main PID: 16063 (kube-apiserver)
CGroup: /system.slice/kube-apiserver.service
└─16063 /usr/bin/kube-apiserver --logtostderr=true --v=0 --etcd_servers=http://127.0.0.1:2379 --address=127.0.0.1 --allow_privileged=false --service-cluster-ip-range=10.254.0.0/16 --admission_contr...All the required services for getting the pod up are running. There is no activity happening, for eg: no image is pulled, neither there is an in entry for pod in kubectl get pod command.
If developers are able to easily deploy a demonstration version of their application/site to a public container based hosting service (e.g. Google Container Engine, the next generation of OpenShift Online), then there are a wide range of public quality assessment services they can take advantage of.
For accessibility testing, the W3C provide some suggested services at http://www.w3.org/wiki/Accessibility_testing#Semi-automated_accessibility_checkers, in particular http://achecker.ca/checker/index.php for WCAG 2.0 compliance checking, and http://juicystudio.com/services/csstest.php for checking perceptibility and scalability of CSS colour choices and font sizes.
Google provides a "mobile friendliness" assessment as part of their webmaster services: https://www.google.com/webmasters/tools/mobile-friendly/ (along with associated documentation: https://developers.google.com/webmasters/mobile-sites/get-started/)
TAW (http://www.tawdis.net/ingles.html?lang=en) offers checkers for WCAG 1.0, WCAG 2.0 and mobile friendliness
(As with #8, the starting point for this would likely just be through documentation, with automated assistance following at a later date)
Friday May 08, 2015 at 14:19 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#7
Currently the default RAM is 512MB. We need to increase it to 2GB at least.
Tuesday May 12, 2015 at 10:28 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#18
We should build an rpm for the atomicapp command and host it in the default dev box, this would help work the entire tool dependencies as well. And can then be tested / validated at the CI level against all the other tests we are running ( eg. the examples and quickstart setups).
Friday May 08, 2015 at 16:39 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#8
Signed-off-by: Lalatendu Mohanty [email protected]
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/8/commits
Wednesday May 20, 2015 at 11:02 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#33
http://apps.openstack.org/ is a new service at openstack.org - we should make sure all our content is easily accessible there.
Saturday Jul 18, 2015 at 07:05 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#45
nitishb included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/45/commits
At least components/rhel-with-docker/docker-host/Vagrantfile seems to.
See https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-January/msg00034.html
As a developer
I run the CDK and
I 'atomic run projectatomic/helloapache',
so that I can access it with my browser running on my laptop
As a developer using windows for development, I want to test my new containers on the CDK. Doing this tests will involve looking at the web interface. Most native way: open the browser on the host and have a look at... ja?! where?
Why? Because this subproject should be about more than shipping a bunch of components as a bundle - it should be about tying them together into a coherent workflow for the development of containerised services intended for eventual deployment on Atomic Host (and potentially other environments).
Monday May 11, 2015 at 10:33 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#9
Signed-off-by: Lalatendu Mohanty [email protected]
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/9/commits
Tuesday May 12, 2015 at 10:25 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#17
It might be a good option to create a second vagrant box that tracks all the upstream versions for the core components we care about here : atomic, kuberneties and docker ( maybe from the virt7-sig ? )
This would be in addition to the default dev box that continues to track downstream versions of these components ( to match the default CentOS-7/x86_64 user experience ).
Friday Jul 17, 2015 at 11:40 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#43
In projectatomic/atomic@c97e5d3 there was an addition of $OPTx feature which lets you to modify labels when running atomic install|run|uninstall|stop commands. We merge the patch for Atomic App using this feate and thus we need to get a newer version of atomic into the dev box.
i.e. newer than commit c97e5d3255b85c715fbbb8e17945beffeefc2332
Monday May 11, 2015 at 16:25 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#14
RHEL is going to release 0.15.0-0.3.git0ea87e4 of kubernetes tomorrow, it will support v1beta3 kubernetes API, we should make a decision if we include kubernetes-0.16.2-2.el7 into the vagrant box.
As of now the vagrantfile [1] does not have Virtualbox support
[1] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/components/centos/centos-with-kubernetes/Vagrantfile.libvirt
Tuesday Jul 28, 2015 at 13:05 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#52
Currently, we are using a disk size of 10GB and we allocate the majority of the space as the output below shows.
$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
LogVol00 VolGroup00 -wi-ao---- 7.97g
LogVol01 VolGroup00 -wi-ao---- 1.50g
docker-pool VolGroup00 twi-aot--- 256.00m 89.06 0.21
As a consequence, the docker-pool starts out very small. We should consider either increasing the size of the disk or resizing LogVol00 down and leaving more space for docker.
Tuesday May 12, 2015 at 11:34 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#19
We might need to get guest additions added to the vbox image, lots of features in vagrant rely on those. eg:
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
Thursday Apr 23, 2015 at 12:51 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#3
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/3/commits
Thursday May 21, 2015 at 14:56 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#34
Could we add the DevAssistant SCL and @tradej's nulecule DAP to the vm?
Monday Apr 20, 2015 at 14:09 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#1
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/1/commits
Thursday Apr 23, 2015 at 12:33 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#2
Signed-off-by: Lalatendu Mohanty [email protected]
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/2/commits
K8s setup is broken after updating to latest k8ns bits of CentOS7 i.e. kubernetes 0:1.0.0-0.8.gitb2dafda.el7
[vagrant@localhost ~]$ kubectl get nodes
error: Failed to negotiate an api version. Server supports: map[v1beta1:{} v1beta2:{} v1beta3:{}]. Client supports: [v1].
The latest build of the atomicapp vagrant box is used [1] for reproducing this issue.
[1] https://cbs.centos.org/koji/taskinfo?taskID=16911 or you can use https://atlas.hashicorp.com/atomicapp/boxes/dev-testing
Steps to reproduce:
[root@xx xxx]# vagrant ssh
[vagrant@localhost ~]$ kubectl get nodes
NAME LABELS STATUS
127.0.0.1 kubernetes.io/hostname=127.0.0.1 Ready
[vagrant@localhost ~]$ sudo yum update -y
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dependency Installed:
python-sqlalchemy.x86_64 0:0.9.8-1.el7
Updated:
atomic.x86_64 0:1.0-108.el7.centos docker.x86_64 0:1.7.1-108.el7.centos docker-python.x86_64 0:1.4.0-108.el7.centos docker-registry.x86_64 0:0.9.1-7.el7
docker-selinux.x86_64 0:1.7.1-108.el7.centos etcd.x86_64 0:2.0.13-2.el7 flannel.x86_64 0:0.2.0-10.el7 kubernetes.x86_64 0:1.0.0-0.8.gitb2dafda.el7
kubernetes-master.x86_64 0:1.0.0-0.8.gitb2dafda.el7 kubernetes-node.x86_64 0:1.0.0-0.8.gitb2dafda.el7 python-websocket-client.noarch 0:0.14.1-108.el7.centos tzdata.noarch 0:2015f-1.el7
[vagrant@localhost ~]$ kubectl get nodes
error: Failed to negotiate an api version. Server supports: map[v1beta1:{} v1beta2:{} v1beta3:{}]. Client supports: [v1].
Restarting the service does not help
[vagrant@localhost ~]$ sudo systemctl restart kube-apiserver.service
[vagrant@localhost ~]$ kubectl get nodes
error: couldn't read version from server: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: connection refused
After yum update, I rebooted the machine and got below error
[vagrant@localhost ~]$ kubectl get nodes
error: couldn't read version from server: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: connection refused
Looks like port 8080 is not available in the vagrant box
[vagrant@localhost ~]$ telnet localhost 8080
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Monday May 18, 2015 at 09:02 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#30
Need below packages so that the AMI image can be put in AWS
Monday May 11, 2015 at 19:20 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#15
include the docker aliases [1] of vpavlin wihtin the base image, they are pretty handy...
[1] - https://github.com/vpavlin/docker-tools/blob/master/bash_aliases_docker
Monday May 11, 2015 at 19:26 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#16
Was thinking it might be nice to ship this vm with a running docker registry (and/or docker-registry-ui ) either direct or in kube. I know I always end up needing one to work on atomicapps, but I think it is arguable.
It would be great to have a single Windows installer that installed:
I'm not sure how to make such a thing myself, but http://wixtoolset.org/ is the approach that's been recommended to me.
Goes here: docs/updating-thebox.rst
Monday May 11, 2015 at 16:25 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#14
RHEL is going to release 0.15.0-0.3.git0ea87e4 of kubernetes tomorrow, it will support v1beta3 kubernetes API, we should make a decision if we include kubernetes-0.16.2-2.el7 into the vagrant box.
I believe we should use a namespace other than atomicapp on atlas.hashicorp.com
Tuesday May 12, 2015 at 13:16 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#20
I am blanking on the term for this, but it would be nice if the ssh and console login messages included displaying the IP of the box. This is actually something I keep meaning to bring up to the cloud sig for both centos and fedora.
We need to update the CentOS Vagrant box information in [1]
[1] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/components/boxes/vagrant-boxes.md
Revok is an open source automated scanner for web service vulnerabilities: https://github.com/Revok-scanner/revok
Integrating that into the developer bundle could potentially make it easier to introduce "design for security" concepts into a workflow.
Since we are using a single box as k8s master and node, we do not need flannel package in the box.
flannel to be used for overlay network provisioning connection between containers pinned on different k8s nodes.
Thoughts?
Monday Jul 27, 2015 at 09:39 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#49
The Docker Daemon port needs to be exposed and TLS certificates made available to the host so that the box can be used as a docker provider on non-linux hosts and so that external tools, such as eclipse can work with the docker daemon in the box.
I believe that by default, we should use port forwarding and create a port on localhost that is forwarded to the docker daemon. We should document using a private_network IP to accomplish the same task. We should also generate a tls certificate pair and place the appropriate component on the host for future use.
A small program or plugin can be to set up environment variables for host consumers.
Opinions/ideas welcome.
While building vagrant box image at koji, python-sqlalchemy package is pulled as dependency for the enlisted packages to be installed in the image.
Repos specified in the koji image build command does not contain python-sqlalchemy package, causing the image to fail, unless added a repo having the package in question.
I'd like to start adding components for working with Fedora and CentOS as well as with RHEL, but would appreciate at least a few clues towards getting started, rather than reverse engineering what I need to add from what's currently there for RHEL :)
Friday May 08, 2015 at 09:17 GMT
Originally opened as LalatenduMohanty/centos7-container-app-vagrant-box#4
LalatenduMohanty included the following code: https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box/pull/4/commits
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.