file to get to it and it hit
me. Super frustrating, but finally got it figured out. Just wanted to say
thanks for all the help!
On Thu, Sep 15, 2016 at 5:10 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
> I don't think that the websocket requests are even hitting the tomcat
>
I don't think that the websocket requests are even hitting the tomcat
application. The access logs show hitting the main page, but nothing
against the websocket itself. It's like it's not getting past the router.
On Thu, Sep 15, 2016 at 4:56 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
com>
wrote:
> The router should support transparent connection upgrade in that case.
> Are you getting any errors in your browser?
>
> On Wed, Sep 14, 2016 at 11:15 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
>> When I deploy it manually (standalone tomcat or
ed up as a named port in the target
> endpoints port list. Required
>
> Set it to "8000".
>
>
> On Wed, Sep 14, 2016 at 10:54 AM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
>> I have an application that runs on tomcat and uses websockets. I'm able
&g
I have an application that runs on tomcat and uses websockets. I'm able to
build it and test it in a standalone docker container and it works fine.
When I deploy that same image to my openshift instance the application can
not connect to the websocket. After doing some research I've found some
to 30 instead of 900. After
restarting it again, it pulled down the image without issue.
As a final test I changed the code, rebuilt the app and docker image and
repushed it to the repository. Within 30 seconds it was detected, pulled
and started deploying.
On Tue, Aug 16, 2016 at 4:36 PM, Tony Saxon
registry.
>
> On Tue, Aug 16, 2016 at 1:59 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
>> Ok, that makes sense. But I am understanding correctly that when you use
>> scheduled=true that it should periodically poll the source registry and
>> pull the lat
wrote:
>
>
> On Aug 16, 2016, at 1:40 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
> Can someone tell me if I'm understanding the difference between alias=true
> and scheduled=true for tagging imagestreams as documented at
> https://docs.openshift.org/latest/dev_gui
the destination when the source is updated, whereas scheduled does
the same thing but only on a periodic basis. Am I off on that?
On Mon, Aug 15, 2016 at 4:04 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
> I'm using a registry deployed from a docker compose:
>
> registry:
>
sableScheduledImport: false
>> maxImagesBulkImportedPerRepository: 5
>> maxScheduledImageImportsPerMinute: 60
>> scheduledImageImportMinimumIntervalSeconds: 900
>>
>> Will take a look and see if I can recreate this issue.
>>
>>
>> On Mon, Aug 1
containers are up. It appears that it's not doing the
periodic import despite being configured to. What is the default period
that it uses to check the source registry?
On Mon, Aug 15, 2016 at 2:29 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
> So I've found that if I tag the imagestream
bbb3d","generation":2}]}]}},{"metadata":{"name":"testwebapp","namespace":"testwebapp","selfLink":"/oapi/v1/namespaces/testwebapp/imagestreams/testwebapp","uid":"dae5b8d1-5fc3-11e6-88da-525400f41cdb
If you
> want to bypass the import by digest, you can use the `--reference` flag
> which only imports the tag name (but includes none of the metadata):
>
> oc tag --reference --source=docker SOME_DOCKER_TAG IMAGESTREAM:TAG
>
>
>
> On Fri, Aug 12, 2016 at 8:58 AM, Tony S
Damn, I just went through having to downgrade my registry because I was
pushing with 1.12 and openshift (running docker 1.10) wasn't able to pull
the image due the the sha256 hash that it was referencing not existing
because of the v1/v2 issues. I guess my only option if I don't want to
upgrade my
2
>
> I'd recommend one of the first two options which will ensure that
> registry stores and serves only manifest v2 schema 1 which is pull-able
> without a problem.
>
> Hope that helps,
> Michal
>
> [1] https://github.com/docker/distribution/blob/master/docs/
> spec/manifest-v2-2.
t;
>> Andy, what would you recommend?
>>
>>
>> On Aug 10, 2016, at 1:58 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>>
>> Ok, maybe that is the issue. I can not do the docker pull referencing the
>> sha256 hash on the node.
>>
>> The docker version runn
testwebapp
Created:Less than a second ago
Labels:
Annotations:
openshift.io/image.dockerRepositoryCheck=2016-08-10T17:01:46Z
Docker Pull Spec: 172.30.11.167:5000/testwebapp/testwebapp
Tag Spec Created
PullSpec
Image
lates
s you should
> fix that.
> 2. Error from server: container "testwebapp" in pod "testwebapp-1-1x7ex"
> is waiting to start: image can't be pulled
>
> First it would be good to get rid of no 1. for the latter I'd need to see
> master logs with loglevel=8 if it's
I'm not sure what I'm missing here. I have a private docker registry that
is set up securely and uses authentication. I followed the docs at
https://docs.openshift.org/latest/dev_guide/managing_images.html#using-image-pull-secrets
to create the secret with the username and password to authenticate
tweaks and I should have it done. Thanks
for your help!
On Thu, Jul 21, 2016 at 4:21 PM, Ben Parees <bpar...@redhat.com> wrote:
>
>
> On Thu, Jul 21, 2016 at 3:55 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
>> Thanks for the help. I'm very close to getting this worki
the current date as default, use `django.utils.timezone.now`
System check identified 1 issue (0 silenced).
July 21, 2016 - 19:29:08
Django version 1.8.4, using settings 'pm_web.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
What is different about t
ea if there's another place to look for logs for what's going wrong?
On Wed, Jul 20, 2016 at 8:45 PM, Ben Parees <bpar...@redhat.com> wrote:
>
>
> On Wed, Jul 20, 2016 at 7:53 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
>> I'm trying to take an existing Django appl
I'm trying to take an existing Django application that we have running on a
system and make it so that I can deploy into a lab origin environment that
I have set up. I started by going through the example Django application:
https://github.com/openshift/django-ex
I didn't have any major problems
e it down
> because it is not actionable in all cases. Would you please file an issue
> regarding this with info about your router?
>
> On Jul 7, 2016, at 2:47 PM, Tony Saxon <tony.sa...@gmail.com> wrote:
>
> I set up an HA router based on the docs at
> https://d
I set up an HA router based on the docs at
https://docs.openshift.org/latest/admin_guide/high_availability.html#admin-guide-high-availability
Everything seemed to work fine, however when I exposed a deployed example I
get an error message in the status:
[root@oso-master ~]# oc status -v
In
25 matches
Mail list logo
