anyone maintaining code for docker containers?

[itaru2622]

I'm using latest codes to get running bluesky on containers in my env.

I found that features can work with dev-env as expected but not with container.
through investigations, I found gaps, such as belows, between code of dev-env and those of containers.

by filling these gaps one by one, the containers got starting to work little by little, but not all features yet.
I guess it need to find all the gaps and feed them back into the container codes to get the full features working on the containers.

---

found gaps regarding atproto/services/bsky/*.js

• it lacks data-plane, bsync, RepoSubscription in atproto/services/bsky/*.js but dev-env has those:
  

  atproto/packages/dev-env/src/bsky.ts

  Lines 43 to 51 in f45eef3

  	const dataplanePort = await getPort()
  	const dataplane = await bsky.DataPlaneServer.create(
  	db,
  	dataplanePort,
  	cfg.plcUrl,
  	)
  	const bsyncPort = await getPort()
  	const bsync = await bsky.MockBsync.create(db, bsyncPort)

  
  

  atproto/packages/dev-env/src/bsky.ts

  Lines 88 to 93 in f45eef3

  	const sub = new bsky.RepoSubscription({
  	service: cfg.repoProvider,
  	db,
  	idResolver: dataplane.idResolver,
  	background: new BackgroundQueue(db),
  	})

• RepoSubscription uses BackgroundQueue but it is not exported then BackgroundQueue cannot be involved from container.
  in dev-env. it is imported as below, with source accessing style.
  

  atproto/packages/dev-env/src/bsky.ts

  Line 9 in f45eef3

  import { BackgroundQueue } from '@atproto/bsky/src/data-plane/server/background'

found gaps on timing of creating DB table( by migrations/*):

• dev-env creates tables earlier than container code, then containers get failure to use DB, but dev-env success.
  earlier creactions are done not just for bsky but also ozone and others.
  

  atproto/packages/dev-env/src/bsky.ts

  Lines 75 to 83 in f45eef3

  	if (cfg.migration) {
  	await migrationDb.migrateToOrThrow(cfg.migration)
  	} else {
  	await migrationDb.migrateToLatestOrThrow()
  	}
  	await migrationDb.close()
  	// api server
  	const server = bsky.BskyAppView.create({

[bnewbold]

The short answer is that running the main branch code directly isn't really supported. We have the dev-env setup for development, and we do "distribution releases" of services like the PDS and Ozone via separate repositories (https://github.com/bluesky-social/pds and https://github.com/bluesky-social/ozone).

The majority of code is in this repository, but supporting folks running the latest version of main at any point of time would be a lot of additional maintenance and support work. You are welcome to try and make it work, but we will probably focus on periodic releases of the "distribution" versions for now.

Another thing to note is that we pretty frequently have large feature branches in this repository, so even main might not be fully up to date.

[itaru2622]

@bnewbold thank you for your response. I understood situation.
at this moment, it needs to deal with individually.
when you got resource, please maintain codes for docker container as part of offical release at timing of assigning versions. since docker is major platform to run software.

[itaru2622]

this post aims to record what it needs for bsky working on docker.

it needs to patch https://github.com/bluesky-social/atproto/blob/main/services/bsky/api.js to involve DB, bsync, dataplane, reposubscription, like dev-env had them.

my patch is located below:
https://github.com/itaru2622/bluesky-selfhost-env/blob/master/patching/105-atproto-services-for-docker.diff

[itaru2622]

closing this topic, by getting current situation described in the above bnewbold's comment.