But it's working fine locally or just with the docker commands. It's because
it's a reverse proxy.
But It's just not working in OpenShift. I can show you the deploymentconfigs:
DC of nodejs
apiVersion: v1
kind: DeploymentConfig
metadata:
annotations:
openshift.io/generated-by: OpenShiftNewA
I'm also not sure what I've to fill in here. So my image is created with this.
This is angular and it contain's the URL of the server where it's running and
its port:
(function () {
'use strict';
angular
.module('app')
.constant('config', {
URL: 'http://ec2xxx-1.compute.amazona
Is your openshift configured to run as root? Try to start nginx
with
-
-user=
$(
id -u).
Maybe nginx is dying because it refuses to start when can't open
error/access log files for writting.
Em 28/01/2016 06:56, "Den Cowboy" escreveu:
> I'm also not sure what I've to fill in here. So my i
Hi,
what I did :
```
$ git clone g...@github.com:openshift/openshift-ansible.git
$ cd openshift-ansible
$ vagrant up --no-provision
$ vagrant provision
$ vagrant ssh master
[root@ose3-master vagrant]# systemctl status etcd.service
● etcd.service
Loaded: not-found (Reason: No such file or direc
On Jan 28, 2016 9:29 AM, "Stéphane Klein"
wrote:
>
> Hi,
>
> what I did :
>
> ```
> $ git clone g...@github.com:openshift/openshift-ansible.git
> $ cd openshift-ansible
> $ vagrant up --no-provision
> $ vagrant provision
> $ vagrant ssh master
> [root@ose3-master vagrant]# systemctl status etcd.se
On Thu, Jan 28, 2016 at 3:31 AM, Den Cowboy wrote:
> But it's working fine locally or just with the docker commands. It's
> because it's a reverse proxy.
> But It's just not working in OpenShift. I can show you the
> deploymentconfigs:
>
> DC of nodejs
> apiVersion: v1
> kind: DeploymentConfig
>
2016-01-28 15:34 GMT+01:00 Jason DeTiberus :
>
> > I look in ```/etc/``` I found nothing about etcd, etcd package isn't
> installed
> >
> > ```
> > [root@ose3-master vagrant]# yum list installed | grep "etcd"
>
> For single master installs, the embedded etcd is used. The embedded etcd
> listens on
On Jan 28, 2016 9:38 AM, "Stéphane Klein"
wrote:
>
>
>
> 2016-01-28 15:34 GMT+01:00 Jason DeTiberus :
>>
>>
>> > I look in ```/etc/``` I found nothing about etcd, etcd package isn't
installed
>> >
>> > ```
>> > [root@ose3-master vagrant]# yum list installed | grep "etcd"
>>
>> For single master in
Hi,
what I did :
```
$ git clone g...@github.com:openshift/openshift-ansible.git
$ cd openshift-ansible
$ vagrant up --no-provision
$ vagrant provision
$ vagrant ssh master
[vagrant@ose3-master ~]$ oc get all
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR
AGE
kubernetes
On Thu, Jan 28, 2016 at 9:46 AM, Stéphane Klein wrote:
> Hi,
>
> what I did :
>
> ```
> $ git clone g...@github.com:openshift/openshift-ansible.git
> $ cd openshift-ansible
> $ vagrant up --no-provision
> $ vagrant provision
> $ vagrant ssh master
> [vagrant@ose3-master ~]$ oc get all
> NAME
I successfully build and push to the registry.
Successfully built eb267616d81c
999 I0128 18:48:08.511970 1 docker.go:95] Pushing image
172.30.137.133:5000/abecorn/tradeclient:latest ...
1000 I0128 18:48:38.886955 1 docker.go:99] Push successful
The deployment log says this:
I0128 18:
Manifest unknown may mean "your registry got deleted or is otherwise
incomplete". Can you pull that image from one of your nodes directly?
On Thu, Jan 28, 2016 at 1:56 PM, Dean Peterson
wrote:
>
> I successfully build and push to the registry.
>
> Successfully built eb267616d81c
> 999 I0128 18:
Ok, that makes sense. I did completely uninstall Docker, then
re-installed. I also removed the volume group Docker was using and re-ran
docker-storage-setup. I was surprised when I brought Openshift back up and
it appeared to retain everything even though I manually removed all
containers and im
I keep seeing this in the openshift console. Is this something to be
concerned about?
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
I had to delete my docker registry and re-install it. It has a new ip
address. However my deployments are still trying to pull from the old ip
address. I restarted Openshift. I thought that is how I fixed this
problem in the past but that does not seem to work.
_
I added a docs bug for this that we can hopefully address while we continue
to work on switching to DNS for talking to the integrated registry:
https://github.com/openshift/openshift-ansible/issues/1297
On Thu, Jan 28, 2016 at 3:14 PM, Dean Peterson
wrote:
> I had to delete my docker registry a
I would imagine the deployments determine where to pull from via the deployment
config
Look at:
oc edit dc
Then look for the old registry IP address. I bet you see it in there several
places.
Gary Franczyk
Senior Unix Administrator, Infrastructure
Availity | 10752 Deerwood Park Blvd S. S
Make that https://github.com/openshift/openshift-docs/issues/1494
On Thu, Jan 28, 2016 at 3:21 PM, Andy Goldstein wrote:
> I added a docs bug for this that we can hopefully address while we
> continue to work on switching to DNS for talking to the integrated registry:
>
> https://github.com/open
Thank!
On Jan 28, 2016 3:03 PM, "Andy Goldstein" wrote:
> Make that https://github.com/openshift/openshift-docs/issues/1494
>
> On Thu, Jan 28, 2016 at 3:21 PM, Andy Goldstein
> wrote:
>
>> I added a docs bug for this that we can hopefully address while we
>> continue to work on switching to DNS
I installed RHEL 7.2 from scratch, then installed Docker and downloaded and
started Openshift 1.1.1. I had been having trouble getting this version to
run reliably. I noticed just recently on startup it was complaining about
port 53 already being bound. I saw that dnsmasq was using the port. I
Port 53 is reserved for the Domain Name System (DNS).
In your case it is the DNS cacher "/usr/sbin/dnsmasq" of the package
dnsmasq-base that's causing this error message.
This pre-installed package is a dependency of network-manager, the
Network Manager of your desktop environment (e.g. Unity, GN
Oh boy, well thank you for the information. I looked at my old machine
running openshift origin 1.0.7 and it has dnsmasq running on port 53 and
things seem to work fine. External traffic routes to my containers running
in openshift. Also, I did have my setup running on this new machine for a
cou
22 matches
Mail list logo
