Adding the registry's address to NO_PROXY in /etc/sysconfig/docker works.
However it doesn't feel like something I should be changing by hand. Is
this something I missed in the ansible configuration when installing?
On 20 September 2016 at 14:09, Lionel Orellana wrote:
> Hi
Hi
I'm getting this error when building the wildfly:10 builder sample on a
containerised v1.3.0.
ushing image 172.19.38.253:5000/bimorl/wildfly:latest ...
Registry server Address:
Registry server User Name: serviceaccount
Registry server Email: serviceacco...@example.org
Registry server
Adding -b=lbr0 --mtu=1450 to the docker daemon options
in /etc/systemd/system/docker.service.d/startup.conf seems to fix it.
The host already had docker installed so perhaps the installation didn't
bother passing or somehow setting those options from
/run/openshift-sdn/docker-network.
On 16
Once more, now with JSON
{
"kind": "List",
"apiVersion": "v1beta3",
"metadata": {},
"items": [
{
"apiVersion": "v1",
"kind": "Pod",
"metadata": {
"labels": {
"name": "node-test"
},
The Swagger GUI is available at this address :
https://openshift-server:8443/swaggerapi
https://www.dropbox.com/s/e0jeow7zoj70oyy/Screenshot%202016-09-19%2019.30.14.png?dl=0
On Mon, Sep 19, 2016 at 7:13 PM, Charles Moulliard
wrote:
> Is swagger packaged with OpenShift
Is swagger packaged with OpenShift Origin to list the operations, ... ?
On Mon, Sep 19, 2016 at 6:45 PM, Clayton Coleman
wrote:
> That is generally the swagger docs (1.2 currently) listed here:
> https://github.com/openshift/origin/tree/master/api/swagger-spec
>
> On Mon,
This is a known issue captured
https://trello.com/c/RLJbg6KX/385-share-kibana-user-dashboard and the
referenced BZ.
Bottom line is to achieve multi-tenancy using the Kibana version provided
by the EFK stack, each user essentially has a 'profile' where there
dashboards and visualizations are
That is generally the swagger docs (1.2 currently) listed here:
https://github.com/openshift/origin/tree/master/api/swagger-spec
On Mon, Sep 19, 2016 at 8:37 AM, Charles Moulliard
wrote:
> Hi,
>
> Is it defined somewhere for each OpenShift Artifacts (Template,
>
When you delete a pod, its containers should **always** be deleted. If they
are not, this is a bug.
Could you please elaborate what use case(s) you have for keeping the
containers around?
Thanks,
Andy
On Mon, Sep 19, 2016 at 5:09 AM, v wrote:
> Hello,
>
> we have an issue
Thx fo the trick Jordan. My problem is solved.
On Mon, Sep 19, 2016 at 2:36 PM, Jordan Liggitt wrote:
> The project already exists (so you get the "already exists" error), and
> the dev user must not have permissions in it.
>
> You'll need to delete it with a more highly
Hi,
I'm confused about this section of the doc : https://github.com/openshift
/jenkins-plugin#jenkins-pipeline-formerly-workflow-plugin
- Is Groovy DSL syntax still supported with Openshift Jenkins Pipeline ?
Additional questions :
- Is it the list of the jenkins plugins that we package with
Hello,
we have an issue with docker/openshfit.
With Openshift 1.1.4 and Docker 1.8.2 we can delete a pod via "oc delete po" and the docker
container is only stopped but not deleted. That means the container is still visible via "docker ps
-a", /var/lib/docker/containers/[hash] still persits,
On Sun, Sep 18, 2016 at 5:12 AM, Dale Bewley wrote:
>
>
> - On Aug 28, 2016, at 9:28 PM, Ben Parees wrote:
>
> https://github.com/sclorg/rhscl-dockerfiles/tree/master/rhel7.s2i-base is
> the future, so you should go off that, which as you noted generates
13 matches
Mail list logo