Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
packer
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
packer
Commits
3d103dcc
Commit
3d103dcc
authored
Jul 24, 2015
by
Chris Bednarski
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #2483 from Xiol/patch-1
Update setup documentation to cover issue #1117
parents
7a6eb966
985c3c57
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
28 additions
and
0 deletions
+28
-0
website/source/intro/getting-started/setup.html.markdown
website/source/intro/getting-started/setup.html.markdown
+28
-0
No files found.
website/source/intro/getting-started/setup.html.markdown
View file @
3d103dcc
...
...
@@ -58,6 +58,34 @@ If you get an error that `packer` could not be found, then your PATH
environment variable was not setup properly. Please go back and ensure
that your PATH variable contains the directory which has Packer installed.
The
`packer`
binary may conflict with the cracklib-supplied packer binary
on RPM-based systems like Fedora, RHEL or CentOS. If this happens, running
`packer`
will result in no output or something like this:
```
text
$ packer
/usr/share/cracklib/pw_dict.pwd: Permission denied
/usr/share/cracklib/pw_dict: Permission denied
```
In this case you may wish to symlink the
`packer`
binary to
`packer.io`
and use that instead. e.g.
```
text
ln -s /usr/local/bin/packer /usr/local/bin/packer.io
```
Then replace
`packer`
with
`packer.io`
when following the rest of the
documentation.
Alternatively you could change your
`$PATH`
so that the right packer
binary is selected first, however this may cause issues when attempting
to change passwords in the future.
```
text
export PATH="/path/to/packer/directory:$PATH"
```
Otherwise, Packer is installed and you're ready to go!
## Alternative Installation Methods
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment