Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

work with containers #62

Closed
dsschult opened this issue Jan 10, 2017 · 8 comments
Closed

work with containers #62

dsschult opened this issue Jan 10, 2017 · 8 comments

Comments

@dsschult
Copy link
Collaborator

Containers are a thing now. NERSC requires them, and I wouldn't be surprised for other sites to follow along.

So, figure out the correct way to submit a glidein inside a container. Mostly it's documentation with an example, but there might be issues with the wrapper script or glidein_start.sh.

@dsschult
Copy link
Collaborator Author

From NERSC:

Found an issue with HTCondor:

01/10/17 12:54:37 my_popenv failed
01/10/17 12:54:37 ERROR "fopen of "/var/run/utmp"" at line 273 in file /home/dschultz/pyglidein/tmp15Mj7h/htcondor-8_4_2/src/condor_sysapi/idle_time.cpp

Apparently we can't map anything in /var into the container for security reasons.

@briedel
Copy link
Contributor

briedel commented Jan 18, 2017

Is that setting from within condor or something we set? We are running a small CoreOS based test cluster using HTCondor without that issue.

@dsschult
Copy link
Collaborator Author

I bet there's a way to turn it off, but we might need to find the right knob. Probably the one to monitor user activity and treat like a workstation that might go back to the user.

@dsschult
Copy link
Collaborator Author

The setting STARTD_HAS_BAD_UTMP = TRUE might do it.

@dsschult
Copy link
Collaborator Author

As noted on #9, we need to fix os_arch.sh to run on docker.

@dsschult
Copy link
Collaborator Author

95e326d fixes os_arch.sh

@hskarlupka
Copy link
Contributor

Submit jobs via Shifter

@dsschult
Copy link
Collaborator Author

closing this ticket in favor of #106, as that's more detailed to the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants