Chapel: Chapel master Docker image?

[tjstavenger-pnnl]

We’re developing against features in the 1.18 pre-release found in the master branch. We had been building on GitlabCI using https://hub.docker.com/r/chapel/chapel/, but since we’ve switched to master the builds are failing as the available Docker images are only for releases.

I could pretty easily make my own Docker image against master, but it would be nice to have an official one. Would it be possible to add a new image that gets updated periodically from master (on commit, nightly, or some other schedule)?

[ben-albrecht]

Design Q: What frequency would work best?

I imagine building nightly images would be easiest implementation-wise.

@awallace-cray seems like the right person to tackle this.

[tjstavenger-pnnl]

How often do your Travis CI builds run? It looks like they're running on commit (which is normally how they work)?

Anyone developing against master would have to expect frequent changes, but some stability through the day would probably be welcome. Anyone needing the latest & greatest would have to wait at most a day. Unless someone is actively working on Chapel & their own code simultaneously, I would think nightly should be acceptable.

[ben-albrecht]

How often do your Travis CI builds run? It looks like they're running on commit (which is normally how they work)?

We run Travis CI sanity checks upon commits, Jenkins smoke tests on 1 configuration post-merge, and Jenkins full testing over all configurations nightly.

[tjstavenger-pnnl]

Ah, so it seems best to rebuild a chapel/chapel:master docker image nightly after you know the Jenkins build has passed. I suspect someone wouldn't want to use a non-functional Chapel Docker image.

[tjstavenger-pnnl]

I forked Chapel so I could add the Dockerfile and use it while we wait for the feature to be included within Chapel itself. See https://github.com/tjstavenger-pnnl/chapel/blob/master/util/dockerfiles/master/Dockerfile

I had thought I'd be able to copy/paste your other Dockerfile and modify it to pull from master instead.

I can successfully create the image, but running start_test outputs this:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_COLLATE = "C",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

For your released images, do you modify the Docker image after building the Dockerfile to correct this?

[awallace-cray]

Do you modify the Docker image after building the Dockerfile to correct this?

No, but the last time I used the Dockerfile was for the last release.
At a guess, we probably need to tweak the Dockerfile for the next release.

From: Tim Stavenger [e-mail]
Reply-To: chapel-lang/chapel [e-mail]
Date: Friday, July 27, 2018 at 1:01 PM
To: chapel-lang/chapel [e-mail]
Cc: Tony Wallace [e-mail], Mention [e-mail]
Subject: Re: [chapel-lang/chapel] Chapel master Docker image? (#10510)

I forked Chapel so I could add the Dockerfile and use it while we wait for the feature to be included within Chapel itself. See https://github.com/tjstavenger-pnnl/chapel/blob/master/util/dockerfiles/master/Dockerfile

I had thought I'd be able to copy/paste your other Dockerfile and modify it to pull from master instead.

I can successfully create the image, but running start_test outputs this:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_COLLATE = "C",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

Do you modify the Docker image after building the Dockerfile to correct this?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chapel-lang/chapel/issues/10510#issuecomment-408524239, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APR3rWI43DDtQROToVTm0wTeGyePkyxKks5uK3FZgaJpZM4VgVDq.

[tjstavenger-pnnl]

Seems like a bit of a kludge, but StackExchange to the rescue! I forced the locale to en_US.UTF-8 and now I don't get the perl warnings.

• https://serverfault.com/questions/362903/how-do-you-set-a-locale-non-interactively-on-debian-ubuntu
• https://serverfault.com/questions/362903/how-do-you-set-a-locale-non-interactively-on-debian-ubuntu#801162

I also set the debian image to v9.4 as it looks like that is what was released back when Chapel 1.17 was released. The debain:stretch image has since changed to v9.5.

I'll get a pull request put together for you.

[tjstavenger-pnnl]

See https://github.com/chapel-lang/chapel/pull/10570

Also https://hub.docker.com/r/pnnl/chapel/tags/

[awallace-cray]

tjstavenger-pnnl - thank you for the updates and the reminder.
I confirmed the perl/locale error with your original Dockerfile (minus the locale change)