-
Notifications
You must be signed in to change notification settings - Fork 16
Singularity container for a Squid proxy #36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: main
Are you sure you want to change the base?
Conversation
…ecause of /cvmfs/ path specified in etc/cvmfs/domain.d/eessi-hpc.org.conf (CVMFS_KEYS_DIR)
config repo *must* be mounted at /cvmfs/cvmfs-config.eessi-hpc.org
…em-layer into cvmfs_proxy_singularity
@@ -0,0 +1,49 @@ | |||
BootStrap: docker | |||
From: centos:7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bedroge Wouldn't it make more sense to make this a Dockerfile, so we can build the Docker image and push it to Docker Hub (and then we can also run it via Singularity)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea! I'll convert it to a Dockerfile.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One disadvantage is that you can't use singularity instance
with a Docker image, since startscript
is not defined in that case...
No description provided.