Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hey i am not able to deploy go app. #6

Open
doloresjose opened this issue Apr 26, 2020 · 11 comments
Open

Hey i am not able to deploy go app. #6

doloresjose opened this issue Apr 26, 2020 · 11 comments

Comments

@doloresjose
Copy link

hey can u tell me why i am not able to deploy certain web apps which earlier was working on zarvus but not now and shows this.
https://m.imgur.com/a/g8k6WD6

plz help me.

@edwin-zvs
Copy link
Contributor

We need little more information about your app.

When your app is deployed correctly, you'll see "Running" link next to your commit, under Deploy tab in the project page. If you click the link you'll get the name of Namespace, such as 'abcd-1-2-3-12345678-abc'.

Could you let me know name of the Namespace your app is running?

@doloresjose
Copy link
Author

actually i deleted the previous one and tried to deploy some other project but was again not able to deploy it so here is the namespace of the new app which i tried to deploy

crtf-1722-416-0-1587943037301-nx5

@edwin-zvs
Copy link
Contributor

The container is OOM killed.
What is really happening behind the scene when a project is build by Buildpacks, system creates Kubernetes Deployment with 2 replica, with 256Mi memory on each container. For now, we don't have memory configuration for Buildpacks.

If this is the case, a workaround could be creating a Kubernetes Deployment manifests (and Service) manually and allocate larger memory (see resources), and deploy using Skaffold. This repository (https://github.com/zarvis-ai/community) deploys documentation using this way.

@doloresjose
Copy link
Author

but earlier they were working fine, so now i have to feed manualy for cpu requirements

@edwin-zvs
Copy link
Contributor

Recently we updated buildpack version, and it might be related. Let us try make deploy through buildpack more stable.

In a long term, deploy through Kubernetes manifest using Skaffold is more recommended while some planned feature (such as persistent storage) will be only available in this way.

@doloresjose
Copy link
Author

thx for the help, btw after u guys updated the buildpack now the deployment is working and also i really liked ur platform.

@doloresjose
Copy link
Author

hey i am again getting the same error as mentioned above, do u know why it is happening

@edwin-zvs
Copy link
Contributor

Hmm. Could you give me a name of the namespace?

@doloresjose
Copy link
Author

doloresjose commented May 28, 2020

here is the namespace

crtf-1673-406-0-1590704760925-hx4

@edwin-zvs
Copy link
Contributor

Containers in the namespace crtf-1673-406-0-1590704760925-hx4 are up and running, everything looks okay. What kind of problem are you experiencing?

@doloresjose
Copy link
Author

whenever i try to access the webapp it gives me 502 error as mentioned above, bit few days back it was working properly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants