public
method but I have not received a response.
Thank you,
Dean Peterson
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
t; enable this. If ES is failing to contact other ES nodes then either there
> is a networking problem or the other nodes aren't listening (yet) on the
> port.
>
> On Thu, Apr 27, 2017 at 10:53 PM, Dean Peterson
> wrote:
>
>> I am trying to start aggregate logging. The e
I am trying to start aggregate logging. The elastic search cluster requires
port 9300 to be open. I am getting Connection refused errors and I need to
open that port. How do I open port 9300 without messing up the existing
rules for Openshift. Do I make changes in firewalld or iptables directly? I
th=1.
> The ref can be a specific commit sha or the name of a branch.
>
> It sounds like an issue on the git server side… I know gogs had an issue
> with this: https://github.com/gogits/gogs/issues/236
>
> Copying Ben for awareness.
>
> On Apr 6, 2017, at 12:40 PM, Dean Peterso
=1 may be what’s throwing it off
>
> On Apr 6, 2017, at 12:24 PM, Dean Peterson
> wrote:
>
> Thank you, that is helpful;
>
> It has been hung for about 5 minutes now. I have included the log in a
> gist:
>
> https://gist.github.com/deanpeterson/6b83f10ae100093f29b2530beb9
it
> clone —recursive —depth=1 [the-url]’ from your local machine?
>
> I suspect that the —depth=1 may be what’s throwing it off
>
> On Apr 6, 2017, at 12:24 PM, Dean Peterson
> wrote:
>
> Thank you, that is helpful;
>
> It has been hung for about 5 minutes now. I have
the BUILD_LOGLEVEL env var to something high:
>
> $ oc set env bc/[your-bc] BUILD_LOGLEVEL=10
>
> On Apr 6, 2017, at 12:00 PM, Dean Peterson
> wrote:
>
> Yes, I can take that exact url and clone at the command line on windows
> and on RHEL 7.3. It only takes about a second.
logs.
Thanks
On Thu, Apr 6, 2017 at 10:51 AM, Cesar Wong wrote:
> Are you able to clone outside of openshift using that URL?
>
> Just looking at what the bad line length character being reported is
> ( of some kind.
>
> On Apr 6, 2017, at 11:43 AM, Dean Peterson
Hi Cesar,
VersionOpenShift Master:v1.4.1Kubernetes Master:v1.4.0+776c994
On Thu, Apr 6, 2017 at 10:19 AM, Cesar Wong wrote:
> Hi Dean,
>
> What version of openshift are you using?
>
> On Apr 6, 2017, at 11:07 AM, Dean Peterson
> wrote:
>
> Hello,
>
> I just i
Hello,
I just installed the latest version of Origin. A build that worked before
is failing with the following:
Cloning "https://someone%40gmail.com:s
omepassword%40morepassword...@enterprisewebservice.kilnhg.com/Code/EnterpriseWebService/Openshift-Docker-Builds/wildfly-jdk-8.git"
...
error: buil
[root@openshift ~]# oc project default
Now using project "default" on server "https://openshift.abecorn.com:8443";.
[root@openshift ~]# oc get services
NAME CLUSTER_IP EXTERNAL_IP PORT(S)
SELECTOR AGE
docker-registry 172.30.219.25 5000/TCP
docker-re
I get this message when I scale down a selenium grid pod. Does anyone know
if this is something to worry about?
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
I pulled down the latest origin openshift-ansible playbooks and ran the
Advanced install. I get the following error:
ansible-playbook ~/openshift-ansible/playbooks/byo/config.yml
statically included:
/root/openshift-ansible/roles/os_firewall/tasks/firewall/firewalld.yml
ERROR! no action detected i
Is this relevant?
https://docs.openshift.org/latest/install_config/redeploying_certificates.html
On Tue, Nov 22, 2016 at 9:16 AM, Dean Peterson
wrote:
> I deleted the route many times. The odd thing is it still serves up the
> same cert with the route deleted. With the route deleted, it s
t; On Nov 22, 2016, at 2:31 AM, Dean Peterson
> wrote:
>
> Is the built in HA Proxy caching the information? How do I clear the
> HAProxy cache in Openshift?
>
> On Tue, Nov 22, 2016 at 1:10 AM, Dean Peterson
> wrote:
>
>> How is this happening? I even remove
check that value for expiration (if your route
> is misconfigured for another reason or has no endpoints).
>
> On Nov 22, 2016, at 2:31 AM, Dean Peterson
> wrote:
>
> Is the built in HA Proxy caching the information? How do I clear the
> HAProxy cache in Openshift?
>
>
Is the built in HA Proxy caching the information? How do I clear the
HAProxy cache in Openshift?
On Tue, Nov 22, 2016 at 1:10 AM, Dean Peterson
wrote:
> How is this happening? I even removed the route entirely; it still shows
> the same certificate information even when showing a 503
the Openshift master and Node.
On Mon, Nov 21, 2016 at 11:05 AM, Dean Peterson
wrote:
> Hello,
>
> I have a route with TLS enabled. The RSA key, certificate and CA bundle
> are all encoded in the route. I have an expiring TLS certificate. I renewed
> and replaced the values of the
Hello,
I have a route with TLS enabled. The RSA key, certificate and CA bundle are
all encoded in the route. I have an expiring TLS certificate. I renewed and
replaced the values of the certificate and CA bundle, removed and updated
the route. Unfortunately, the browser still shows the same expira
The containers being run, even the build containers, cannot resolve
internal network hosts. For example, a proxy server sits at a specific
internal host url (only seen on the internal network). Openshift creates
containers on its own subnetwork. The containers on the Openshift network
cannot see th
Thu, Oct 13, 2016 at 3:58 PM, Jason DeTiberus
wrote:
>
>
> On Thu, Oct 13, 2016 at 4:48 PM, Dean Peterson
> wrote:
>
>> Our machines use rhn classic. If I try to run subscription-manager
>> register it says I am already registered with redhat classic. However, this
>> do
gt; determines if the data is wiped when the PVC is released. The default
>> value is "Retain". It will not delete the data unless you set it to
>> "Recycle".
>>
>> https://docs.openshift.com/enterprise/3.0/admin_guide/persis
>> tent_storage_nfs.
at 3:29 PM, Kent Perrier wrote:
> subscription-manager is used to register your host to your local satellite
> as well. How are you patching your hosts if they are not registered?
>
> Kent
>
> On Thu, Oct 13, 2016 at 3:05 PM, Dean Peterson
> wrote:
>
>> Can anyone
Can anyone please help? We use satellite for access to our software. We do
not use subscription-manager. Unfortunately when running docker builds, the
containers cannot access the hosts registries because they expect to access
auto attached subscription-manager subscriptions
How is openshift suppos
If I create a persistent volume claim using an NFS share that has existing
data, will the data be wipded? Same thing with creating the persistent
volume. Will the existing data be deleted. I want to make existing data
accessible to multiple pods/containers in an NFS share. If I make a
persistent vo
Ok, apparently it was hung up on some previous failed login for some
reason. It seems to be working now. Thanks for the help and more info on
how to trouble shoot this. It helped regardless.
On Mon, Oct 10, 2016 at 10:43 AM, Dean Peterson
wrote:
> It appears those match. From what I can t
Mon, Oct 10, 2016 at 10:38 AM, Jordan Liggitt
wrote:
> The URL shown in the user's browser should be the "public master url"
> given to the configuration.
>
>
> On Mon, Oct 10, 2016 at 11:33 AM, Dean Peterson
> wrote:
>
>> The machine reaches out to the pu
The machine reaches out to the public web by proxy server. Do I need to add
the proxy server url as a valid redirectURI?
On Mon, Oct 10, 2016 at 10:13 AM, Dean Peterson
wrote:
> It looks like the URLs in the web-console config and master-config.yaml
> are correct. Is there something els
It looks like the URLs in the web-console config and master-config.yaml are
correct. Is there something else that can cause this?
On Oct 10, 2016 9:51 AM, "Dean Peterson" wrote:
> Attached is the contents of my master-config.yaml
>
> On Mon, Oct 10, 2016 at 9:21 AM, Dea
client/openshift-web-console
> -o yaml` would help
>
>
>
> On Mon, Oct 10, 2016 at 9:10 AM, Dean Peterson
> wrote:
>
>> This is a complete showstopper, does anyone have any ideas?
>>
>> On Oct 9, 2016 8:51 PM, "Dean Peterson" wrote:
>>
>
This is a complete showstopper, does anyone have any ideas?
On Oct 9, 2016 8:51 PM, "Dean Peterson" wrote:
> [image: Inline image 2]
>
> I get the above error when I have standard username and password
> authentication with htpasswd enabled as well as when I have aut
[image: Inline image 2]
I get the above error when I have standard username and password
authentication with htpasswd enabled as well as when I have authentication
disabled entirely and use AllowAll. Nothing I do seems to get around this
error. I have installed openshift with the ansible installer
/openshift-cluster/roles/cockpit/tasks/main.yml*
with
a file that forces cockpit verison 103.
On Sun, Oct 9, 2016 at 11:33 AM, Dean Peterson
wrote:
> I get an error saying cockpit-shell version 103 is requires but version
> 114 is installed. I tried removing 114 and installing 103, but a
I get an error saying cockpit-shell version 103 is requires but version 114
is installed. I tried removing 114 and installing 103, but ansible
overrides the version again during install and the same error occurs. I
even tried the enterprise version and used the quick installer. It also
uses ansib
Hello,
Our open shift server is behind a proxy inside our corporate network
We are finding that there are all kinds of things that do not work unless
they can connect to the internet.
I see the documentation here:
https://access.redhat.com/documentation/en/openshift-container-platform/3.3/pa
Thank you! That makes sense. I just wanted to get an expert opinion.
On Wed, Oct 5, 2016 at 3:15 PM, Ben Parees wrote:
>
>
> On Oct 5, 2016 4:05 PM, "Dean Peterson" wrote:
> >
> > Does it make sense to spin up multiple Jenkins instances in a single
> pod?
Does it make sense to spin up multiple Jenkins instances in a single pod?
For example. If I use the built in Jenkins template and spin it up. Then
click the arrow to increase the number of pods/containers running Jenkins,
will this cause issues due to the stateful nature of Jenkins?
___
9, 2016 at 10:17 AM, Dean Peterson
> wrote:
>
>> I normally set openshift up on physical machines. However, I am now
>> trying to get things working on an AWS EC2 instance. I notice the instance
>> immediately overwrites any changes I make to resolv.conf. I am not able
behavior? Do
> we see a 503 page from the haproxy router?
>
>
>
> --
> John Skarbek
>
> On May 29, 2016 at 23:23:57, Dean Peterson (peterson.d...@gmail.com)
> wrote:
>
> Yes, that works:
>
> oc get routes
> NAME HOST/PORT
, Skarbek, John wrote:
> That’s weird, that should’ve worked… What about simply oc get routes
>
>
>
> --
> John Skarbek
>
> On May 29, 2016 at 23:19:40, Dean Peterson (peterson.d...@gmail.com)
> wrote:
>
> is the command correct? i just get "Error from server:
is the command correct? i just get "Error from server: routes
"–-all-namespaces" not found"
On Sun, May 29, 2016 at 10:15 PM, Skarbek, John wrote:
> What do we see when we do a:
>
> oc get routes –all-namespaces
>
>
>
> --
> John Skarbek
&g
roups: system:cluster-admins
system:cluster-readers
system:masters
system:nodes
system:routers
On Sun, May 29, 2016 at 8:06 PM, Dean Peterson
wrote:
> Yes, the route url is pointing at the public ip address of my ec2 instance:
>
> [ec2-user@ip-172-31-15-150 ~]$ sudo
do an nslookup or dig using the dns name provided by the
> route, does it resolve to the public IP of your instance?
>
>
>
> --
> John Skarbek
>
> On May 29, 2016 at 20:14:27, Dean Peterson (peterson.d...@gmail.com)
> wrote:
>
> It seems every time I install open
It seems every time I install openshift everything goes perfectly, right up
until I add a route and try to reach any of my services. I installed with
ansible using the stock openshift ansible playbook. After I installed I
completed the setup for AWS configuration. Everything is running. I am
ab
I see the following errors when I try to tart my node after installing
Openshift Origin with the Ansible installer and following the extra
instructions here:
https://docs.openshift.org/latest/install_config/configuring_aws.html
I was able to get openshift up, a router and registry installed, but I
I normally set openshift up on physical machines. However, I am now trying
to get things working on an AWS EC2 instance. I notice the instance
immediately overwrites any changes I make to resolv.conf. I am not able to
reach and routes I set on my services. Otherwise everything seems to be
insta
se code: 500
3scripts.js:239 WebSocket connection to 'wss://
openshift.enterprisewebservice.com:8443/oapi/v1/namespaces/abecorn/bu…ase-build-3-build&access_token=UP5Zl2jMDor122SaSHZVcOgekphjqLiksns-yLNTFsU'
failed: Error during WebSocket handshake: Unexpected response code: 500
On S
I just installed a new Openshift Origin (latest version) on an EC2 instance
in AWS. Logs have always just worked for me. I am trying to view the logs
in the web console for a build but only see "Logs are not available The
logs are not available or could not be loaded" What might be the cause of
th
tps://docs.openshift.org/latest/install_config/master_node_configuration.html#node-configuration-files
> see annotation #4. This will limit the amount of storage each project
> can allocate on emptydir in order to push your applications towards
> using proper persistent volumes.
>
> On Tue, May 17,
When I installed Openshift Origin I first installed Docker and ran
"docker-storage-setup" to make docker use a dedicated lvm volume group I
created (4TB). However, Openshift Origin seems to be storing everything on
my root partition (rhel-root) that only has 50GB!
To find this out I discovered a
Hello,
I have a very large drive dedicated to the private registry using docker
storage. However, the kubernetes backing openshift origin seems to be
eating up my rhel-root. Using du -hx --max-depth=1 / I was able to track
down the culprit. Kubernetes.io~empty-dir is eating up all my space on
r
Nevermind, I figured it out.
On Mon, May 2, 2016 at 11:45 PM, Dean Peterson
wrote:
> I did a rollback on a service. Now I want the latest version. However,
> when I do a build now, it doesn't trigger a deployment and nothing I do
> seems to make the deployments use the latest bu
I did a rollback on a service. Now I want the latest version. However,
when I do a build now, it doesn't trigger a deployment and nothing I do
seems to make the deployments use the latest build. Is there a way to fix
this?
___
users mailing list
users@
I get this error when migrating my database and upgrading to 1.9.3:
"Property 'databaseSchema' needs to be specified in the configuration
I have this in my keycloak-server.json file:
"connectionsMongo": {
"default": {
"host": "xx.xx.xx.xx",
"port": "27017",
I get the following error just trying to build the images:
Completed, with errors
Failed to create logging-dev-build-template in project Logging.
Cannot create image stream "centos". ImageStream "centos" is invalid:
spec.dockerImageRepository: Invalid value: "library/centos:7": the
repository name
e build scripts and or the buildconfigs defined in the
> hack directory.
>
> On Thu, Mar 10, 2016 at 5:32 PM, Dean Peterson
> wrote:
>
>> I am getting the following error in the event logs when I go to deploy
>> the elasticsearch pods after running the logging-deployer:
&
I am getting the following error in the event logs when I go to deploy the
elasticsearch pods after running the logging-deployer:
Error syncing pod, skipping: failed to "StartContainer" for "elasticsearch"
with ImagePullBackOff: "Back-off pulling image \"logging-elasticsearch\
However, there is n
Mar 4, 2016, at 12:31 AM, Dean Peterson
> wrote:
>
> In previous versions of openshift origin I was able to run an nginx server
> with some static content inside a container. Now I install with the
> ansible installer and I get the following error in the nginx errors.log
> inside th
In previous versions of openshift origin I was able to run an nginx server
with some static content inside a container. Now I install with the
ansible installer and I get the following error in the nginx errors.log
inside the running container.
2016/03/03 23:51:22 [emerg] 6#0: setgid(996) failed
},
"port": {
"targetPort": "web"
}
},
"status": {
"ingress": [
{
"host": "home.enterprisewebservice.com",
"routerName": "router",
tes.io/serviceaccount/token)"
> or the variant I was using with a "<" instead of cat to have bash read
> it:
> curl -k -vvv https://openshift.abecorn.com:8443/api/v1/routes/ -H
> "Authorization: Bearer $(< /var/run/secrets/
> kubernetes.io/serviceaccoun
io/serviceaccount/token)"
> or the variant I was using with a "<" instead of cat to have bash read
> it:
> curl -k -vvv https://openshift.abecorn.com:8443/api/v1/routes/ -H
> "Authorization: Bearer $(< /var/run/secrets/
> kubernetes.io/serviceaccount/tok
the variant I was using with a "<" instead of cat to have bash read
>> it:
>> curl -k -vvv https://openshift.abecorn.com:8443/api/v1/routes/ -H
>> "Authorization: Bearer $(< /var/run/secrets/
>> kubernetes.io/serviceaccount/token)"
>>
>> Does that wo
-account=router
>
> commands that expect a username use the calculated username for the
> service account, e.g. `oadm policy add-cluster-role-to-user system:router
> system:serviceaccount:default:router`
>
> Also, do you need to `cat` the service account token in the command, like
Content-Type: application/json
< Date: Thu, 03 Mar 2016 18:20:09 GMT
< Content-Length: 247
<
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "User \"sys
The logs only say: "Router is including routes in all namespaces"
On Thu, Mar 3, 2016 at 10:22 AM, Jordan Liggitt wrote:
> What is in your router logs?
>
> On Thu, Mar 3, 2016 at 11:21 AM, Dean Peterson
> wrote:
>
>> *The service account does exist:*
>>
Ram actually went through quite a lot with me last night. Here is a gist
of the irc chat:
https://gist.github.com/deanpeterson/568f07b032933e9d219b
On Thu, Mar 3, 2016 at 10:36 AM, Dean Peterson
wrote:
> The logs only say: "Router is including routes in all namespaces"
>
&
-admins
system:cluster-readers
system:masters
system:nodes
Still getting 503 error on all services
On Thu, Mar 3, 2016 at 10:14 AM, Dean Peterson
wrote:
> Now when it displays:
>
> oadm policy who-can get endpoints --all-namespaces Namespace:
>
>
n Thu, Mar 3, 2016 at 10:16 AM, Dean Peterson
> wrote:
>
>> Yes, it only shows this:
>>
>> oadm policy who-can get endpoints --all-namespaces
>> Namespace:
>> Verb: get
>> Resource: endpoints
>>
>> Users: router
>>
Actually, I just noticed; router is in there.
On Thu, Mar 3, 2016 at 9:16 AM, Dean Peterson
wrote:
> Yes, it only shows this:
>
> oadm policy who-can get endpoints --all-namespaces
> Namespace:
> Verb: get
> Resource: endpoints
http://fpaste.org/332733/45699454/
>
>
> The token info from inside the router container (/var/run/secrets/
> kubernetes.io/serviceaccount/token) seems to work if I use it
> with oc login but not with the curl command - so it feels a bit odd. Any
> ideas what's amiss he
The router is on default namespace but the service pods are running on a
different namespace.
On Thu, Mar 3, 2016 at 1:53 AM, Julio Saura wrote:
> seems your router is running on default namespace, your pods are also
> running on namespace default?
>
>
> El 3 mar 2016, a las 7:58
e router service account has no permissions to get
> the routes/endpoints info from etcd.
> Check that the router service account (router default or whatever service
> account you used to start the router) is
> part of the privileged SCC and has read permissions to etcd.
>
>
> O
quot;)
>
> nsenter> curl -vvv -H "Host: "
> http[s]://:
> # you can use:
> # cat /var/lib/haproxy/conf/haproxy.config to get the servers for a
> backend
> # and
> # cat /var/lib/conf/haproxy/conf/*.map for the backend / hostname.
>
>
>
oxy.config
> # router-pod-name as shown in oc get pods
>
> Ram//
>
> On Wed, Mar 2, 2016 at 10:10 PM, Dean Peterson
> wrote:
>
>> I ran that "oc env dc router RELOAD_INTERVAL=5s" but I still get the 503
>> error. Do I need to restart anything?
>>
&
192.168.1.0/19.
On Thu, Mar 3, 2016 at 12:10 AM, Dean Peterson
wrote:
> I ran that "oc env dc router RELOAD_INTERVAL=5s" but I still get the 503
> error. Do I need to restart anything?
>
> On Wed, Mar 2, 2016 at 11:47 PM, Ram Ranganathan
> wrote:
>
>> Dean, we di
ou have a custom deployment config then replace the dc name
> router to that deployment config name.
>
> and see if that helps.
>
>
> On Wed, Mar 2, 2016 at 6:21 PM, Dean Peterson
> wrote:
>
>> Is there another place I can look to track down the problem? The rou
Is there another place I can look to track down the problem? The router
logs don't say much, just: " Router is including routes in all namespaces"
On Wed, Mar 2, 2016 at 7:39 PM, Dean Peterson
wrote:
> All it says is: " Router is including routes in all namespaces"
All it says is: " Router is including routes in all namespaces" That's it.
On Wed, Mar 2, 2016 at 7:38 PM, Clayton Coleman wrote:
> What do the router logs say?
>
> On Mar 2, 2016, at 7:43 PM, Dean Peterson wrote:
>
> This is as close to having openshift ori
router many times before and never had this issue. I've had issues with
other parts of the system but never the router.
On Wed, Mar 2, 2016 at 6:34 PM, Dean Peterson
wrote:
> I have a number of happy pods. They are all running normally.
>
> On Wed, Mar 2, 2016 at 6:28 PM,
ar 2, 2016 at 7:03 PM, Dean Peterson
> wrote:
>
>> I have successfully started the ha proxy router. I have a pod running,
>> yet all my routes take me to a 503 service unavailable error page. I
>> updated my resolv.conf file to have my master ip as nameserver; I've nev
I have successfully started the ha proxy router. I have a pod running, yet
all my routes take me to a 503 service unavailable error page. I updated
my resolv.conf file to have my master ip as nameserver; I've never had this
problem on previous versions. I installed openshift origin 1.1.3 with
an
Yes, thank you that works! I was not aware of those commands.
On Wed, Mar 2, 2016 at 5:11 PM, Mohamed Lrhazi <
mohamed.lrh...@georgetown.edu> wrote:
> systemctl restart origin-master
> and/or
> systemctl restart origin-node
>
> don't work?
>
> On Wed, Mar 2
I installed openshift origin with ansible. Unlike the binary I didn't seem
to need to run "openshift start" to start Openshift. When I needed to
restart openshift I would find the openshift process and kill it and the
openshift process would automatically start back up. It is no longer
starting
I didn't change any of my templates and the nocache and forcepull options
seem to be ignored in openshift origin v1.3.1.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
If I install openshift origin using the ansible installer, where can I find
the logs for the running master?
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
he SDN configuration may be disabling
> your network, or some other unexpected interaction with the host is
> blocking traffic.
>
> On Mon, Feb 22, 2016 at 1:23 PM, Dean Peterson
> wrote:
> > Any ideas how the ansible installer may have made my machine
> inaccessible to
> >
Any ideas how the ansible installer may have made my machine inaccessible
to the outside world even with iptables turned off?
On Feb 21, 2016 10:57 PM, "Dean Peterson" wrote:
> I performed an ansible install of openshift origin. If I am on the local
> machine, I can bring up
I wonder if splitting the imagestream, build and deployment config from the
service and routes into separate templates is my problem too:
https://bugzilla.redhat.com/show_bug.cgi?id=1303273
I switched to ansible install hoping that would solve my problem by
eliminating something I may have done wr
I performed an ansible install of openshift origin. If I am on the local
machine, I can bring up openshift in the browser. However, on any external
machine, I am no longer able to access anything on the openshift master. I
am unable to ssh, or visit the openshift web console in a browser. I
che
ically configured dnsmasq
> for you.
>
> On Fri, Jan 29, 2016 at 12:16 AM, Dean Peterson
> wrote:
> > 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 se
Actually, I meant I changed runAsUser to runAsAny in scc restricted.
On Sat, Feb 6, 2016 at 10:48 PM, Dean Peterson
wrote:
> The last time I had containers starting and the logs were blank I needed
> to set the runAsUser to runAsAny because I use root inside my docker
> files. I che
The last time I had containers starting and the logs were blank I needed to
set the runAsUser to runAsAny because I use root inside my docker files. I
checked that setting and the scc privileged file is set to runAsAny.
On Sat, Feb 6, 2016 at 10:36 PM, Dean Peterson
wrote:
> The container
a oc logs) show?
>
> On Feb 5, 2016, at 10:16 AM, Dean Peterson
> wrote:
>
> I am still evaluating Openshift for use with the State of MN. I am
> testing it on a separate project of mine. I was fairly impressed with
> Openshift until I started having significant problems with
I opened a ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=1303273
On Fri, Jan 29, 2016 at 9:07 PM, Dean Peterson
wrote:
> I also noticed, the deployments keep saying say are trying to use the
> oldest image id even though there have been many subsequent successful
> builds
I just don't get why sometimes it works and sometimes it doesn't. The
latest random error is this in the event logs:
Failed to pull image "
172.30.250.187:5000/abecorn/tradeclient@sha256:cbca9d885bf1c23bb518662cc51d61b5365ab321147a59d2be5b86869f50c08e":
Driver devicemapper failed to create image
> Otherwise, consider the following comments - http://bit.ly/23x4NK2 -
> before attempting to remove dnsmasq-base or kill port 53.
>
> Sincerely,
>
> Mike
> On 01/28/2016 10:03 PM, Dean Peterson wrote:
> > I installed RHEL 7.2 from scratch, then installed Docker and downloaded
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
> 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
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.
_
1 - 100 of 116 matches
Mail list logo
