Skip to content

Commit

Permalink
[#52] move to docker compose plugin syntax
Browse files Browse the repository at this point in the history
  • Loading branch information
trel committed Nov 20, 2023
1 parent a790fa3 commit 0ebfbc2
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,12 +25,12 @@ $ git submodule update --init

To run all services:
```bash
$ docker-compose up
$ docker compose up
```

To run an individual service (and all services on which it depends):
```bash
$ docker-compose up <service-name>
$ docker compose up <service-name>
```

For example, this command will spawn containers for the following services:
Expand All @@ -42,7 +42,7 @@ For example, this command will spawn containers for the following services:
5. `irods-client-zmt`

```bash
$ docker-compose up irods_client_zmt
$ docker-compose up irods-client-zmt
```

For more information about Compose CLI options, see Docker Compose documentation: https://docs.docker.com/engine/reference/commandline/compose
Expand Down Expand Up @@ -73,5 +73,5 @@ $ sudo umount ./irods_client_nfsrods/nfs_mount

The NFSRODS service maps the `/etc/passwd` file on the host machine to the `/etc/passwd` file in the container providing the service. The user(s) accessing the mountpoint will need to exist as iRODS users as well in order to be able to interact with the mountpoint. This can be done by running the following command on the host machine for each `username` which needs to be mapped:
```bash
$ docker exec irods_demo_irods-client-icommands_1 iadmin mkuser <username> rodsuser
$ docker exec irods_demo-irods-client-icommands-1 iadmin mkuser <username> rodsuser
```

0 comments on commit 0ebfbc2

Please sign in to comment.