Skip to content

Commit 4123a4c

Browse files
committed
Revert "Merge pull request osg-htc#316 from mwestphall/SOFTWARE-6256-ospool-ep-ubuntu"
This reverts commit d32a6a4, reversing changes made to 01f3a4c.
1 parent d32a6a4 commit 4123a4c

1 file changed

Lines changed: 0 additions & 68 deletions

File tree

‎docs/resource-sharing/os-backfill-containers.md‎

Lines changed: 0 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -112,11 +112,6 @@ On EL hosts, the pilot container can also be managed via a systemctl service pro
112112
Running the Container with Docker
113113
---------------------------------
114114

115-
!!! note "Linux Flavor"
116-
The instructions in this section pertain to running the OSPool EP container on an EL-based
117-
host such as AlmaLinux. [Additional considerations](#running-with-docker-on-ubuntu)
118-
are required for running on Ubuntu and other Debian-based Linux flavors.
119-
120115
The Docker image is kept in [DockerHub](https://hub.docker.com/r/opensciencegrid/osgvo-docker-pilot).
121116
In order to successfully start payload jobs:
122117

@@ -177,69 +172,6 @@ to mount [CVMFS using cvmfsexec](#cvmfsexec) and invoke `singularity` for user j
177172
Singularity (now known as Apptainer) allows OSPool users to use their own container for their job (e.g., a common use case for GPU jobs).
178173
See [Advanced: Pod Security](#advanced-pod-security-configuration) for more details.
179174

180-
### Running with Docker on Ubuntu
181-
182-
!!! warning "Removing AppArmor Restrictions"
183-
AppArmor is a security layer on Ubuntu and other Debian-based systems that interferes with container-based jobs
184-
running inside the OSPool EP container. The section below describes removing all restrictions that AppArmor would
185-
normally place on the OSPool EP container. While other isolation mechanisms that Docker places between the host
186-
and container remain intact in this configuration, the degree of isolation is lessened by removing AppArmor.
187-
188-
189-
On Ubuntu and other Debian-based systems, the default [AppArmor profile](https://apparmor.net/) may prevent Singularity jobs from running inside your
190-
EP containers. This is a confirmed issue on Ubuntu 24.04+. The restrictions that Appormpor places on the OSPool EP container may be removed as follows:
191-
192-
1. Install `apparmor-utils` via apt.
193-
194-
:::console
195-
root@ubuntu # apt-get install apparmor-utils
196-
197-
1. Create a `docker-ep` apparmor profile with all restrictions lifted in `/etc/apparmor.d/docker-ep.profile`:
198-
199-
include <tunables/global>
200-
201-
profile docker-ep flags=(attach_disconnected, mediate_deleted) {
202-
# Allow all rules
203-
capability,
204-
network,
205-
mount,
206-
remount,
207-
umount,
208-
pivot_root,
209-
ptrace,
210-
signal,
211-
dbus,
212-
unix,
213-
file,
214-
}
215-
216-
1. Install the AppArmor profile:
217-
218-
:::console
219-
root@ubuntu # apparmor_parser -r /etc/apparmor.d/docker-ep.profile
220-
root@ubuntu # aa-enforce /etc/apparmor.d/docker-ep.profile
221-
222-
1. Update the Docker command from the previous section to use this unrestricted AppArmor profile.
223-
224-
```hl_lines="6"
225-
docker run -it --rm --user osg \
226-
--pull=always \
227-
--security-opt seccomp=unconfined \
228-
--security-opt systempaths=unconfined \
229-
--security-opt no-new-privileges \
230-
--security-opt apparmor=docker-ep \
231-
--device /dev/fuse \
232-
-v /path/to/token:/etc/condor/tokens-orig.d/flock.opensciencegrid.org \
233-
-v /worker-temp-dir:/pilot \
234-
-e GLIDEIN_Site="..." \
235-
-e GLIDEIN_ResourceName="..." \
236-
-e GLIDEIN_Start_Extra="True" \
237-
-e OSG_SQUID_LOCATION="..." \
238-
-e CVMFSEXEC_REPOS=" \
239-
oasis.opensciencegrid.org \
240-
singularity.opensciencegrid.org" \
241-
hub.opensciencegrid.org/osg-htc/ospool-ep:24-release
242-
```
243175

244176
Optional Configuration
245177
----------------------

0 commit comments

Comments
 (0)