diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2019-10-11 04:24:42 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-11 04:24:42 -0700 |
| commit | 43dcc917aed8208ffec99b50e469da03ef34d9e8 (patch) | |
| tree | 70de97fd68dc428f753a282805782262a3f3713d /troubleshooting.md | |
| parent | 6d35eac6a35bb3343314dd27cb4c921fb44bba19 (diff) | |
| parent | 8bfa4c975ba65f51a2bff4bb6dc42170eb736d37 (diff) | |
| download | podman-43dcc917aed8208ffec99b50e469da03ef34d9e8.tar.gz podman-43dcc917aed8208ffec99b50e469da03ef34d9e8.tar.bz2 podman-43dcc917aed8208ffec99b50e469da03ef34d9e8.zip | |
Merge pull request #4205 from manics/no-log-init
troubleshooting: fix useradd no-log-init argument
Diffstat (limited to 'troubleshooting.md')
| -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 |