Hey,
for all the curious people out there:
Just wanted to say that pulling via oc new-app or oc run did not work for my
v1.2.1 cluster any more after I used this trick.
On top of that this trick has permanently messed up something in my cluster because "oadm prune images
--confirm" now randoml
This is the string flag bug again. We really need to fix this.
On Aug 10, 2016, at 4:04 AM, Cesar Wong wrote:
Lionel,
So is it working for you now?
On Aug 9, 2016, at 11:10 PM, Lionel Orellana wrote:
Digging through the go libraries used for parsing the command options I
found that setting
Yes.
On 10 August 2016 at 18:04, Cesar Wong wrote:
> Lionel,
>
> So is it working for you now?
>
> On Aug 9, 2016, at 11:10 PM, Lionel Orellana wrote:
>
> Digging through the go libraries used for parsing the command options I
> found that setting the no_proxy variable like this works:
>
> -e \
Lionel,
So is it working for you now?
> On Aug 9, 2016, at 11:10 PM, Lionel Orellana wrote:
>
> Digging through the go libraries used for parsing the command options I found
> that setting the no_proxy variable like this works:
>
> -e \"no_proxy=172.17.0.3,172.17.0.4\"
>
> It all comes down
Digging through the go libraries used for parsing the command options I
found that setting the no_proxy variable like this works:
-e \"no_proxy=172.17.0.3,172.17.0.4\"
It all comes down to https://golang.org/pkg/encoding/csv
which is used by the pflag package.
On Tue, 9 Aug 2016 at 10:31 PM, Lio
Setting the log level to 4 I found the following
Starting OpenShift using container 'origin'
I0809 22:21:26.415373 20151 run.go:143] Creating container named "origin"
config:
image: openshift/origin:v1.3.0-alpha.2
command:
start
--master-config=/var/lib/origin/openshift.local
I guess what I need is a way to configure the proxy as per
https://docs.openshift.org/latest/install_config/http_proxies.html#configuring-hosts-for-proxies
On Tue, 9 Aug 2016 at 10:05 AM, Lionel Orellana wrote:
> It's been difficult to get a functional poc going with oc cluster up
> behind a pro
It's been difficult to get a functional poc going with oc cluster up behind
a proxy.
I need to maintain the registry's address so I can add it to the no_proxy
variable of the docker deamon. Clayton's procedure works for reusing the
address . I will try --use-existing-config.
But I also need to ad
Generally deep configuration is not the goal of oc cluster up - that's more
the Ansible installs responsibility. oc cluster up is about getting a
running cluster up for test / dev as quickly as possible, but we don't want
to add fine grained tuning to it.
On Mon, Aug 8, 2016 at 10:49 AM, Cesar Wo
Hi Lionel,
You can always reuse the same data/config dirs and keep your service ips:
oc cluster up --host-data-dir=blah --host-config-dir=blah --use-existing-config
> On Aug 7, 2016, at 9:17 PM, Lionel Orellana wrote:
>
> Thanks Clayton.
>
> Would be nice to have a way of setting the address
Thanks Clayton.
Would be nice to have a way of setting the address when using cluster up
though.
On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman wrote:
> When you create the registry you can specify the service IP that is
> assigned (as long as another service hasn't claimed it).
>
> $ oadm
When you create the registry you can specify the service IP that is
assigned (as long as another service hasn't claimed it).
$ oadm registry -o yaml > registry.yaml
$ vi registry.yaml
# Set the registry service `spec.clusterIP` field to a valid service IP
(must be within the service CI
Hi
I'm facing a similar problem to this:
https://github.com/openshift/origin/issues/7879
Basically I need to configure the NO_PROXY variable of the Docker deamon to
include the registry address. Problem is with cluster up I can't control
the ip address that will be assigned to the registry. Or at
13 matches
Mail list logo
