diff options
| author | Simon Li <spli@dundee.ac.uk> | 2019-10-05 23:51:38 +0100 |
|---|---|---|
| committer | Simon Li <orpheus+devel@gmail.com> | 2019-10-06 12:21:06 +0100 |
| commit | 8bfa4c975ba65f51a2bff4bb6dc42170eb736d37 (patch) | |
| tree | d5a9c7d28ec90b89d66a5f48abe46bc8800253c7 | |
| parent | 2c2782a2179aee6c76d90e864708e2e5ceb09349 (diff) | |
| download | podman-8bfa4c975ba65f51a2bff4bb6dc42170eb736d37.tar.gz podman-8bfa4c975ba65f51a2bff4bb6dc42170eb736d37.tar.bz2 podman-8bfa4c975ba65f51a2bff4bb6dc42170eb736d37.zip | |
troubleshooting: fix useradd no-log-init argument
--log-no-init should be --no-log-init
Signed-off-by: Simon Li <spli@dundee.ac.uk>
| -rw-r--r-- | troubleshooting.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/troubleshooting.md b/troubleshooting.md index 89c850356..6fed719f7 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -142,7 +142,7 @@ If you are using a useradd command within a Dockerfile with a large UID/GID, it #### Solution -If the entry in the Dockerfile looked like: RUN useradd -u 99999000 -g users newuser then add the `--log-no-init` parameter to change it to: `RUN useradd --log-no-init -u 99999000 -g users newuser`. This option tells useradd to stop creating the lastlog file. +If the entry in the Dockerfile looked like: RUN useradd -u 99999000 -g users newuser then add the `--no-log-init` parameter to change it to: `RUN useradd --no-log-init -u 99999000 -g users newuser`. This option tells useradd to stop creating the lastlog file. ### 7) Permission denied when running Podman commands |