1
0
mirror of https://github.com/rancher/os.git synced 2025-08-11 11:32:28 +00:00

Remove -d flag from ros serivice up in docs

This commit is contained in:
Josh Curl 2016-11-20 20:19:53 -08:00
parent 4d9b2595b8
commit 4abc6dd4d1
No known key found for this signature in database
GPG Key ID: 82B504B9BCCFA677
5 changed files with 10 additions and 10 deletions

View File

@ -13,7 +13,7 @@ DKMS is supported by running the DKMS scripts inside a container. To compile any
``` ```
# Installing Kernel Headers for Docker # Installing Kernel Headers for Docker
$ sudo ros service enable kernel-headers $ sudo ros service enable kernel-headers
$ sudo ros service up -d kernel-headers $ sudo ros service up kernel-headers
# Run a container in Docker and bind mount specific directories to run DKMS # Run a container in Docker and bind mount specific directories to run DKMS
$ docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10 sh -c 'apt-get update && apt-get install -y sysdig-dkms' $ docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10 sh -c 'apt-get update && apt-get install -y sysdig-dkms'
``` ```
@ -23,7 +23,7 @@ $ docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10
``` ```
# Installing Kernel Headers for System Docker # Installing Kernel Headers for System Docker
$ sudo ros service enable kernel-headers-system-docker $ sudo ros service enable kernel-headers-system-docker
$ sudo ros service up -d kernel-headers-system-docker $ sudo ros service up kernel-headers-system-docker
# Run a container in System Docker and bind mount specific directories to run DKMS # Run a container in System Docker and bind mount specific directories to run DKMS
$ sudo system-docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10 sh -c 'apt-get update && apt-get install -y sysdig-dkms' $ sudo system-docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10 sh -c 'apt-get update && apt-get install -y sysdig-dkms'
``` ```

View File

@ -17,14 +17,14 @@ The following commands can be used to install kernel headers for usage by contai
``` ```
$ sudo ros service enable kernel-headers $ sudo ros service enable kernel-headers
$ sudo ros service up -d kernel-headers $ sudo ros service up kernel-headers
``` ```
#### System Docker #### System Docker
``` ```
$ sudo ros service enable kernel-headers-system-docker $ sudo ros service enable kernel-headers-system-docker
$ sudo ros service up -d kernel-headers-system-docker $ sudo ros service up kernel-headers-system-docker
``` ```
The `ros service` commands will install the kernel headers in `/lib/modules/$(uname -r)/build`. Based on which service you install, the kernel headers will be available to containers, in Docker or System Docker, by bind mounting specific volumes. For any containers that compile a kernel module, the Docker command will need to bind mount in `/usr/src` and `/lib/modules`. The `ros service` commands will install the kernel headers in `/lib/modules/$(uname -r)/build`. Based on which service you install, the kernel headers will be available to containers, in Docker or System Docker, by bind mounting specific volumes. For any containers that compile a kernel module, the Docker command will need to bind mount in `/usr/src` and `/lib/modules`.

View File

@ -12,11 +12,11 @@ In order to start using ZFS, you'll need to first enable one of the [persistent
``` ```
$ sudo ros console switch ubuntu $ sudo ros console switch ubuntu
$ sudo ros service enable kernel-headers $ sudo ros service enable kernel-headers
$ sudo ros service up -d kernel-headers $ sudo ros service up kernel-headers
$ sudo ros service logs kernel-headers $ sudo ros service logs kernel-headers
``` ```
When RancherOS console has reloaded, you will have logged into the persistent console. The current kernel headers will need to be downloaded using the `ros service enable` and the service will be started with `ros service up -d kernel-headers`. When RancherOS console has reloaded, you will have logged into the persistent console. The current kernel headers will need to be downloaded using the `ros service enable` and the service will be started with `ros service up kernel-headers`.
You can make sure that the headers are in the right place by looking at the kernel-headers service logs. You can make sure that the headers are in the right place by looking at the kernel-headers service logs.

View File

@ -24,7 +24,7 @@ disabled open-vm-tools
# Enable a system service # Enable a system service
$ sudo ros service enable kernel-headers $ sudo ros service enable kernel-headers
# Start a system service # Start a system service
$ sudo ros service up -d kernel-headers $ sudo ros service up kernel-headers
``` ```
### Disabling and Removing System Services ### Disabling and Removing System Services

View File

@ -41,12 +41,12 @@ $ sudo ros service enable https://mydomain.com/example.yml
<br> <br>
After the custom system service is enabled, you can start the service using `sudo ros service up -d <serviceName>`. The `<serviceName>` will be the names of the services inside the `docker-compose.yml`. After the custom system service is enabled, you can start the service using `sudo ros service up <serviceName>`. The `<serviceName>` will be the names of the services inside the `docker-compose.yml`.
``` ```
$ sudo ros service up -d nginxapp $ sudo ros service up nginxapp
# If you have more than 1 service in your docker-compose.yml, add all service names to the command # If you have more than 1 service in your docker-compose.yml, add all service names to the command
$ sudo ros service up -d service1 service2 service3 $ sudo ros service up service1 service2 service3
``` ```
### Launching Services from a web repository ### Launching Services from a web repository