You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4123a4c
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/resource-sharing/os-backfill-containers.md
-68Lines changed: 0 additions & 68 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,11 +112,6 @@ On EL hosts, the pilot container can also be managed via a systemctl service pro
112
112
Running the Container with Docker
113
113
---------------------------------
114
114
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
-
120
115
The Docker image is kept in [DockerHub](https://hub.docker.com/r/opensciencegrid/osgvo-docker-pilot).
121
116
In order to successfully start payload jobs:
122
117
@@ -177,69 +172,6 @@ to mount [CVMFS using cvmfsexec](#cvmfsexec) and invoke `singularity` for user j
177
172
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).
178
173
See [Advanced: Pod Security](#advanced-pod-security-configuration) for more details.
179
174
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`:
0 commit comments