Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
ecb6d132
Commit
ecb6d132
authored
Mar 05, 2019
by
Ismo Puustinen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
hack/lib/util.sh: fix empty array expansion with bash 3.
parent
257205d6
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
1 deletion
+3
-1
util.sh
hack/lib/util.sh
+3
-1
No files found.
hack/lib/util.sh
View file @
ecb6d132
...
@@ -649,7 +649,9 @@ EOF
...
@@ -649,7 +649,9 @@ EOF
# Determines if docker can be run, failures may simply require that the user be added to the docker group.
# Determines if docker can be run, failures may simply require that the user be added to the docker group.
function
kube::util::ensure_docker_daemon_connectivity
{
function
kube::util::ensure_docker_daemon_connectivity
{
IFS
=
" "
read
-ra
DOCKER
<<<
"
${
DOCKER_OPTS
}
"
IFS
=
" "
read
-ra
DOCKER
<<<
"
${
DOCKER_OPTS
}
"
DOCKER
=(
docker
"
${
DOCKER
[@]
}
"
)
# Expand ${DOCKER[@]} only if it's not unset. This is to work around
# Bash 3 issue with unbound variable.
DOCKER
=(
docker
${
DOCKER
[@]
:+
"
${
DOCKER
[@]
}
"
}
)
if
!
"
${
DOCKER
[@]
}
"
info
>
/dev/null 2>&1
;
then
if
!
"
${
DOCKER
[@]
}
"
info
>
/dev/null 2>&1
;
then
cat
<<
'
EOF
' >&2
cat
<<
'
EOF
' >&2
Can't connect to 'docker' daemon. please fix and retry.
Can't connect to 'docker' daemon. please fix and retry.
...
...
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