providing access with docker

9
Providing Access with Docker Proof of Concept [Matthew] Farrell 14 January 2016 Image: General Library Exterior, before 1948. Source: Duke University Archives. License: cc-by-nc-sa. CurateGear UNC-Chapel Hill

Upload: others

Post on 16-Oct-2021

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Providing Access with Docker

Providing Access with Docker

Proof of Concept[Matthew] Farrell

14 January 2016

Image: General Library Exterior, before 1948. Source: Duke University Archives. License: cc-by-nc-sa.

CurateGear

UNC-Chapel Hill

Page 2: Providing Access with Docker

Our Current Access System

• Limited application access

• Web restricted to localhost

• Disable optical burner

• Disable printer admin

• Disabled Airport

• Block all incoming connections

• Moved peripheral drivers

Images: Reading room access terminal, Rubenstein

Library.

Page 3: Providing Access with Docker

ASpace-->Aeon Requests

Summer 2015: tweaked finding aid stylesheet spawns

Aeon requests from digital object URIs in ASpaceImage: Screen capture of Guide to the Stephanie Strickland Papers, 1955-2015, Rubenstein Library, Duke University.

License: CC-BY-NC.

Page 4: Providing Access with Docker

Aeon request

Image: Screen capture of Aeon Request for Electronic Records.

Page 5: Providing Access with Docker

Potential Solution: Docker + noVNC

Images: Docker and VNC Web Client noVNC. Source: Linux Screenshots, 2013-2014. License: CC-BY-2.0.

Page 6: Providing Access with Docker

Data Volume Container

• Docker ADD

statements for some

• wget for others

• Multiple collections

possible

• Note: objects not

behind access wall,

currently

Page 7: Providing Access with Docker

Access container

• Forked from Mark McCahill’sproject

• Add software required for viewing files, ex:

– xpdf

– DOSbox

• Container mounts specific volumes from the data container

• Uses noVNC to create desktop environment

• Creates desktop shortcut to the data directory

Page 8: Providing Access with Docker

S#!t Still TBD

• Authentication I:

preservation repository

• Authentication II: user

auth into system

• OS-specific files

• Complex emulated

environments

• Automated generation

• Persistence, or the lack

thereof

• Flexible file permissions

• Multiple VMs running

concurrently?

• What should users do

with the stuff once they

get it?

Page 9: Providing Access with Docker

Thanks!

[email protected]

@laissezfarrell

http://github.com/laissezfarrell/docker-novnc-trials