Unable to start pageserver using docker-compose

[william-lbn]

Steps to reproduce

follow https://github.com/neondatabase/neon/blob/main/docs/docker.md on mac pro

Expected result

neon work it.

Actual result

neon pageserver failed.

By checking docker-compose.yml, it was found that the pageserver had modified the startup method, but no entry for the startup command was found


Add the startup command and enter the container to view

The file mounting is correct

Pageserver is missing a startup command? or Is there no command to start the pageserver?

What is the startup command for pageserver？

[problame]

Likely the new identity.toml file is missing in your existing data directory.

https://discord.com/channels/1176467419317940276/1184894814769127464/1266346201234804827

Heads up self-hosted / neon_local users: we've moved the id= field of the pageserver configuration to a new configuration file identity.toml, which sits next to pageserver.toml.

To continue using your neon_local environment, make the following changes (assuming you are using NEON_REPO_DIR=.neon):

• cargo neon stop
• create new file identity.toml
• move the id= line from pageserver.toml
• cargo neon start

Here's the epic with more context in case you're interested: #7736

[problame]

Also, please provide the pageserver log output.

[william-lbn]

Pageserver startup failed with no log output.

I'm not sure where to go to check the logs, so I modified the image startup method and went to check. I found that the files were mounted correctly.

Do you know how to see the logs？

I see it has restarted dozens of times in a short period of time. It would be great if I could see the logs.

Or could you tell me the startup command for the page server so that I can try it out in the container.

[jcsp]

@william-lbn FYI, we recently added a README in docker-compose/ to clarify the limited scope of the compose file:

The configuration in this directory is used for testing Neon docker images: it is
not intended for deploying a usable system. To run a development environment where
you can experiment with a minature Neon system, use cargo neon rather than container images.

There has been some discussion on the #neon-oss discord channel (https://discord.gg/92vNTzKDGp) about creating a kubernetes operator for running Neon services, which would provide a nicer way to manage compatibility of things like config files -- currently the neon binaries have backward compatibility for things like configs for about 2 weeks, as we release the code into our production environment at least weekly (but are open to working with the community on approaches to make things easier for self-hosted folks)