Fix build warning

[bb03]

[WARNING]: Empty continuation line found in:
RUN sed -i -e 's/%!s(MISSING)udo\s+ALL=(ALL(:ALL)?)\s+ALL/%!s(MISSING)udo ALL=NOPASSWD:ALL/g' /etc/sudoers && sudo echo -e '\nansible ALL=(splunk)NOPASSWD:ALL' >> /etc/sudoers && groupadd -r ${ANSIBLE_GROUP} && useradd -r -m -g ${ANSIBLE_GROUP} ${ANSIBLE_USER} && usermod -aG sudo ${ANSIBLE_USER} && mkdir ${CONTAINER_ARTIFACT_DIR} && chown -R ${ANSIBLE_USER}:${ANSIBLE_GROUP} $CONTAINER_ARTIFACT_DIR && chmod -R 555 ${SPLUNK_ANSIBLE_HOME} && chmod 755 /sbin/entrypoint.sh /sbin/createdefaults.py /sbin/checkstate.sh
[WARNING]: Empty continuation lines will become errors in a future release.

[nwang92]

This looks to be a docker engine syntactical warning: moby/moby#35387 which looks like we'd just need to cleaning our RUN commands

[nwang92]

I'm also not seeing this anymore, but I'm running Docker CE for Mac using edge versions:

Step 39/43 : RUN sed -i -e 's/%sudo\s\+ALL=(ALL\(:ALL\)\?)\s\+ALL/%sudo ALL=NOPASSWD:ALL/g' /etc/sudoers     && sudo echo -e '\nansible ALL=(splunk)NOPASSWD:ALL' >> /etc/sudoers     && groupadd -r ${ANSIBLE_GROUP}     && useradd -r -m -g ${ANSIBLE_GROUP} ${ANSIBLE_USER}     && usermod -aG sudo ${ANSIBLE_USER}     && mkdir ${CONTAINER_ARTIFACT_DIR}     && chown -R ${ANSIBLE_USER}:${ANSIBLE_GROUP} $CONTAINER_ARTIFACT_DIR     && chmod -R 555 ${SPLUNK_ANSIBLE_HOME}     && chmod -R 777 ${CONTAINER_ARTIFACT_DIR}     && chmod 755 /sbin/entrypoint.sh /sbin/createdefaults.py /sbin/checkstate.sh
 ---> Running in 3322d1308447
Removing intermediate container 3322d1308447
 ---> 91e28d6b8b71
Step 40/43 : USER ${ANSIBLE_USER}
 ---> Running in 639bd4a8d03d
Removing intermediate container 639bd4a8d03d
 ---> 062aa5d37cb9
Step 41/43 : HEALTHCHECK --interval=30s --timeout=30s --start-period=3m --retries=5 CMD /sbin/checkstate.sh || exit 1
 ---> Running in d690df31dc36
Removing intermediate container d690df31dc36
 ---> 6d6a82204171
Step 42/43 : ENTRYPOINT [ "/sbin/entrypoint.sh" ]
 ---> Running in c06ab92470da
Removing intermediate container c06ab92470da
 ---> 797388080f16
Step 43/43 : CMD [ "start-service" ]
 ---> Running in b49446d92438
Removing intermediate container b49446d92438
 ---> 92ce1cb2ac2a
Successfully built 92ce1cb2ac2a
Successfully tagged splunk-debian-9:latest

$ docker version
Client: Docker Engine - Community
 Version:           19.03.0-rc2
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        f97efcc
 Built:             Wed Jun  5 01:37:53 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.0-rc2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       f97efcc
  Built:            Wed Jun  5 01:42:10 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

[bb03]

Looks like its still happening on our circleci machines https://circleci.com/gh/splunk/docker-splunk/350 so lets change the focus of the ticket to update our build images