Wordpress example for DCOS 1.11 #353
Conversation
wordpress/1.11/README.md
Outdated
|
|
||
| - We need to customize our mysql service for further development. I will explain it later. | ||
| - Go to `mysql` service from services menu, click on `Edit` button. | ||
| - Chnage `Container Runtime` from `Docker Engine` to `Universal Container Runtime(UCR)`. |
wordpress/1.11/README.md
Outdated
|
|
||
| - We need to customize our mysql service for further development. I will explain it later. | ||
| - Go to `mysql` service from services menu, click on `Edit` button. | ||
| - Chnage `Container Runtime` from `Docker Engine` to `Universal Container Runtime(UCR)`. |
There was a problem hiding this comment.
Testing under 1.11.2, the "Edit" menu off of the services menu just brings you back to the original configuration screens for the service. Where are you finding the screen to change which container runtime is being used?
Also, a little thing: typo for the word "Change"
There was a problem hiding this comment.
Here, I am talking about editing mysql service after it is up and running. It is the only way currently possible to change container runtime. There is no way to set container runtime when we deploy our service from GUI and CLI. Does that answer your question?
There was a problem hiding this comment.
Can you explain exactly how you get to this screen? When I click "Edit" I get the original setup menu, not one that lets me edit the containerizer.
There was a problem hiding this comment.
I deployed mysql service and select it from services. then clicked on Edit button from right top corner, it is same screen as we can edit any other services, on left side, there are options like Service, Placement, Networking etc.
There was a problem hiding this comment.
Hopefully we can get to the bottom of this, I took a screencast of what I'm seeing on the open source version of DC/OS 11.2, which seems different from yours: https://www.youtube.com/watch?v=YNq8A63zgAs
wordpress/1.11/README.md
Outdated
| "name": "wordpress", | ||
| "username": "wp_admin", | ||
| "password": "password", | ||
| "root_password": "wordpress" |
There was a problem hiding this comment.
Just noting that this does differ slightly from the screenshot above, where the root password was unchanged.
There was a problem hiding this comment.
sorry, my mistake. I was doing some experiment and forgot to change back.
wordpress/1.11/README.md
Outdated
|
|
||
| - Now, as we can see, everything is setup but there is no js, css support on our wordpress website because according to database, they are on different path. So we have to change our database url to load wordpress theme files like js, css, images. | ||
|
|
||
| - In order to change values in database, we have to go into mysql service container and change the values. DC/OS currently only support UCR(Uninversal Container Runtime), if we want to go inside the deployed container. It is the reason first we customized our mysql service right after we deployed it. Currently, there is no way that we can set our deployment service runtime to UCR. So we have to set it after we deployed it. Read more about this [here](https://docs.mesosphere.com/1.11/deploying-services/containerizers/). |
There was a problem hiding this comment.
Spelling typo on "Universal"
|
So, I figured out what's going on here. As of 1.11, the Marathon definition is no longer directly accessible via the DC/OS UI anymore like it was in 1.10, which is why I'm only seeing the configuration for the package itself and can't edit the containerizer. The workarounds are either to use the CLI to make changes to the Marathon definition, or to use the Marathon UI instead (accessible via /marathon/ in the DC/OS UI). |
|
Hey, sorry I was a little busy. Using CLI, it is still not working. I changed the container type to
|
|
I believe this blank screen issue was one that was addressed in a recent UI update. And the CLI method should work unless something else changed. I'm wondering if editing through the marathon web UI would yield better results? Thanks again for all your work on this, I'll see about chatting with the team responsible for this package if we can't find a good solution. |
|
I've also seen that behaviour when deploying the percona-mongo package via the CLI, although only when I did dcos package describe --config > options.json and then passing the options.json to package install. |
added wordpress example
Issue #337