-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve ubuntu 22.04 support #1
Comments
I'm familiar with the issue, which is why I have defaulted both Mongo7 and Mongo8 linux binaries to ubuntu-22.04 |
Oh cool, I'll try it out tomorrow in our tests and let you know |
Swapping out EphemeralMongo in our tests seems to not work I'm just getting timeout errors waiting for the db to start - both linux (in container apps build pipeline) and osx (rider)
I also get nothing logged to the test if I set up the stdout logger |
From what i can see all the packages put the right things in the right places, and our config is fairly simple
|
Which MongoDB.Driver version are you using? |
I tried both 7 and 8 with the same result |
No, I meant the MongoDB.Driver nuget package, which version is referenced in your project? |
oh sorry - 3.0.0 |
Just to eliminate any counfounding issues I created a new test project with just a single test:
and i get the same behaviour |
and the file listing looks all good for finding the runtimes
|
Can you please try removing |
still errors with no options at all [Test]
public void Test1()
{
MongoRunner.Run(new MongoRunnerOptions()
{
//UseSingleNodeReplicaSet = true,
StandardOuputLogger = TestContext.WriteLine,
//AdditionalArguments = "--nojournal"
});
} |
That's odd, I was sure that the "--nojournal" option is what caused it, as I tested it and it gave me the same error.
|
@rbev Any luck? If not, can you please create a minimal reproduction. |
The minimal replication is literally just consume the nuget package But here you go: |
You're right, that's very minimal. Can you please try running mongod manually and check the output: .\mongod --dbpath ./db --tlsMode disabled --port 51401 --bind_ip 127.0.0.1 You'll need to create an empty db directory. |
I'm on an M2 mackbook pro Do you need to include osx-arm64 as it's own package? |
Also forcing it to run under x64 does not work
|
Yes, that's the issue. ARM 64 is not supported as explained here. |
i'm not sure that makes sense - we've been running this on apple silicon for literally years with no issues something has changed |
Which version of MongoDB were you running? |
Can you verify your setup against this compatibility table? |
ok - so if i downgrade MongoSandbox to use mongod v6.x it works fine on my laptop my OSX version ( |
interestingly changing it to mongo v8 works for me and according to my colleague my replication demo passes on their M1 macbook pro, so it's something with mongod7 + M2 |
That's good, we're making progress. |
maybe a bad binary from the mongoDB release? edit: actually that makes no sense |
Ok, so the OSX issue aside - the current 1.0.0 build does NOT work on a 22.04 ubuntu image. I've just pushed a MongoSandbox8 build of my tests up and it doesn't work, in fact it seems to just lock up. |
That is likely an issue with the code, the github workflow pipeline tests all nuget packages against windows and linux environments, and I'm using MongoSandbox8 in multiple microservices that are developed on windows and deployed and tested in linux pipelines, all without issues. Try pushing the minimal reproduction up instead and see if it passes then work your way from there. |
In case anyone comes across this issue wondering what the resolution was
|
FYI having issues with MongoSandbox6 on GitHub Actions ubuntu-latest (which are now running Ubuntu 24.04.1) similar errors to those listed above), but MongoSandbox8 seems ok. |
MongoDB 6 goes EoL in July - and I don't think it's supported on that version of linux |
there is a long standing issue with newer linux distributions in EphemeralMongo that I can only assume still exists in this fork
asimmon/ephemeral-mongo#51
asimmon/ephemeral-mongo#48 (comment)
I believe that this issue really just stuck around becuase the older ubuntu was needed to run MondoDB 4 - which is now EoL, so the linux-x64 pacakge can probably be updated to work on newer Ubuntu.
The text was updated successfully, but these errors were encountered: